Behind a corporate proxy – Git

.gitconfig

[credential]
helper = manager
[url "https://"]
insteadOf = git:/
[url "https://github.com/"]
insteadOf = git@github.com:
[http]
proxy = http://username:password@xxx.xxx.xxx.xxx:xxxx
[https]
proxy = http://username:password@xxx.xxx.xxx.xxx:xxxx

If you are using macOS, change the credential from manager to osxkeychain.

[credential]
helper = osxkeychain

angular-cli@webpack – add API proxy

Create a file like “proxy.json” in your angular-cli@webpack projects’ root.

{
  "/api": "http://localhost:1337"
}

start your development server with:

🍰  $ ng serve –proxy-config proxy.json

All request to

http://localhost:4200/api/v1/endpoint

will now be proxied to

http://localhost:1337/api/v1/endpoint

 

Pro Tip:

add

"start": "ng serve --proxy-config proxy.json",

to the scripts section inside of your package.json and use the following command for development: ;-)

npm start

Delete a remote Git tag

Because i have to look it up all the time (and WS has no UI support AFAIK)…

If you created a tag like ‘mytag’ you can delete it by running:

git tag -d mytag
git push origin :refs/tags/mytag

That will remove ‘mytag’ from your local and the remote repository.

Your Lead Architect Doesn’t Really Understand Microservices

http://thenewstack.io/genius-techie-doesnt-really-understand-cloud

There is no doubt that hype trumps learning, and that’s just a fact; we have a wealth of available and immediate information now in the Internet age. It takes time for experts to discern what matters and what does not. But in the end, following the leader may be the best approach of all.

I’ve seen this exact same story so many times in the wild. Many companies (mostly enterprises) still don’t get their mind shifted from the old “this-is-my-application” (monolithic) to a new service oriented “cloud” architecture.

Developers still tend to think about it like the SOA approach they learned in a training (or at university) many years ago… but just inside their own world. So at the end, they often come up with a largely decoupled monolith, that still heavily depends on that one database or a “special” system configuration to make that application work.