Boolean was acquired by Cohr and is in placed in long term archival mode.
No more blog posts will be added but it will continue to be online for as long as analytics tell us that visitors find the archives useful…
Thanks for everything.
Prior to Sierra keys were persisted between logins – and with an update to ssh Keychain is no longer used by default. It can get frustrating to be prompted to enter your passphrase for a key after an upgrade and after each restart.
In your ~/.ssh/config file you will need the following lines:
Host *
UseKeychain yes
AddKeysToAgent yes
IdentityFile ~/.ssh/id_rsa
Change ~/.ssh/id_rsa to the filename of your private key and if you utilise multiple keys also add an IdentityFile line for each of them.
You also need to initially add the key to save the passphrase to Keychain for the first time using:
ssh-add -K ~/.ssh/id_rsa
Sourcetree is a great free git GUI client for Mac and Windows. A recent update (2.4) really broke my workflow however and it took me longer than it should have to figure out what the issue was.
It seems Atlassian are enforcing a behavioural naming convention for ssh keys, which seems somewhat crazy. Rather than go through and change all my own naming conventions to align with theirs I simply created some symlinks. Problem solved.
The format needed is: yourbitbucketusername-BitBucket.pub
Given the syntax for creating a symbolic link:
ln -s /path/to/original/ /path/to/link
You’ll need something along the lines of:
ln -s ~/.ssh/id_rsa.pub ~/.ssh/boolean-BitBucket.pub
An upstream provider will be performing server upgrades during the following window:
Start: 2016-06-15 00:00 UTC
End: 2016-06-15 04:00 UTC
Sites will be powered off and unavailable for approximately 5 minutes during this window. Please plan accordingly.
An upstream provider will be performing maintenance to access switches during the following window:
Maintenance start: 2015-09-30 21:30 UTC
Maintenance end: 2015-09-30 21:45 UTC
The systems will remain powered on but network connectivity will drop for 2-5 minutes. Please plan accordingly.
An upstream provider will be performing software upgrades to server hypervisors during the following window:
Maintenance start: 2015-09-03 01:00 UTC
Maintenance end: 2015-09-03 08:00 UTC
The systems will remain powered on but network connectivity will drop for 2-5 minutes. Please plan accordingly.
An upstream provider will be performing software upgrades to core network routers during the following window:
Maintenance start: 2015-04-14 20:00 UTC
Maintenance end: 2015-04-15 02:00 UTC
It is not expected that there will be any impact to customers.
Recently there was a critical vulnerability in git announced affecting many git users including myself on OSX.
After downloading and installing the latest version of git and entering in Terminal
git −−version
I was presented with the incorrect version number. Checking where it had been installed with
which git
displayed the original
/usr/bin/git
instead of the newly installed version at
/usr/local/git/bin
To resolve this I added the correct path (to my bash profile)
export PATH="/usr/local/git/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:$PATH"
and now which git correctly returned the new path and bumped the version
git version 2.0.1
