Free as in beer.
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
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.
Nice introduction to RxJSÂ by Gerard Sans.
Gerard is awesome, i had the pleasure to talk (and have a beer) with him during angularconnect in 2015.
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.
Yesterday i found this one in my archives. It is a clip made out of many images, that have been taken during the development of COPE at Bechtle back in 2014/2015.
If you like it and want to create something like this on your own. Here is a short step by step guide on how to do it on Mac OS X.
Step 1: Install imagesnap
brew install imagesnap
Step 2: Create post-commit hook
Add the following code from the gist below to a file called  post-commit in your repo’s ~/.git/hooks/ folder.
Step 3: Enable permissions
Lets give the file some permission (making it executable by everyone).
sudo chmod +x ~/.git/hooks/post-commit
Step 4: Start committing and smilingÂ
On first run, the script will create a folder called commit_images in your repo’s root. Then every time you commit code, a photo is added to the folder and to.gitignore automatically so you don’t have to.
Current Downfall
The only downfall to this solution is you have to add it to each of your git repos manually. So if you have a lot of repos it might be a pain, but then again thats what writing a script is for, right? So behold…the global solution (for new repos)!
Global Solution
1. Enable git templates. This will copy everything in the .git-templates folder to any new git repositories when you git init
git config --global init.templatedir '~/.git-templates'
2. Create our hooks folder for the post-commit template.
mkdir -p ~/.git-templates/hooks
3. Add the post-commit file in ~/.git-templates/hooks/. We can use the same script from above in step 2.
4. Make our post-commit executable. We are giving it executable permission to all users in this case.
sudo chmod +x ~/.git-templates/hooks/post-commit
5. Start committing and smiling. Every time we  git init, we now have the post-commit hook in all of our new repos.
Nice to Have
Here are some things I am looking into:
