I like SourceTree because it provides an intuitive interface for all the git commands that I don’t remember, especially for advanced merges, etc…
This quick shortcut will help you open SourceTree from your terminal. Note, you can probably do this with other git clients. The breakdown is using the
-a is just specifying the application.
open -a SourceTree /path/to/repoalias sourcetree='open -a SourceTree'
Then you can do:
If you’re already in your repo directory you can do:
BTW, you can also use this to open finder
MacOS has KeyChain built into terminal
How to store your sensitive credentials to keychain
security add-generic-password -a "$USER" -s 'name_of_your_key' -w 'passphrase'
How to retrieve them from your keychain
security find-generic-password -a "$USER" -s 'name_of_your_key' -w
How to set this up in your
.bash_profile so that you can actually use this:
NAME_OF_YOUR_KEY=$(security find-generic-password -a "$USER" -s "name_of_your_key" -w)
Now you can do something like
echo $NAME_OF_YOUR_KEY and see your secret with your bash_profile being safe.
So, we’ve recently run into some interesting issues where we’ve been using GCP’s Loadbalancers on Kubernetes and serving an API endpoint that uses websockets.
The Problem: GCP LoadBalancers are not by default configured to handle websockets and optimized for http calls, because by default the load balancers have 30 second timeouts in place that causes connections to close.
This will walk you through how to setup a load balancer, ingress, and configure it for you so that you stop getting timeout outs when web-sockets ping. …