More features than you need, but I’ll bet it also has the ones you do need and can’t get anywhere else. I have some deep misgivings about the decision of Homebrew to take exclusive ownership of /usr/local, but on a fresh install of macOS, if you’re prepared to let Homebrew have its way, there is no simpler/faster way of installing a bunch of necessary and useful command line packages ( here’s a snapshot of my Brewfile). ![]() Ok, so this one is not a GUI app, but it’s very important, as it is the primary way of getting all the not-GUI apps (and a few of the GUI ones too), so including it here. plugging in or unplugging an external display, or launching an app). I use it for positioning windows using hot keys and in response to events (eg. Programmable macOS automation and scripting tool. I mostly use Chrome itself, but sometimes use Chrome Canary too. Not as pretty as Apple’s own Safari, but despite the fact it shares many internals, 2012 was the year I finally had to recognize that Chrome had gotten the edge in features and stability. Software in this list is either open source, or otherwise freeware/donationware. I’m not mentioning here command-line apps like Git, tmux and Vim - which I also consider to be essential - but am instead confining myself to GUI apps only.īasically, this is the stuff that I end up installing on every machine that comes into my possession, and which I would be sad about if it ever became abandonware. Not sure why it’s needed.This is a list of software which I consider to be pretty much a "must have" on any Mac I own. I saw others write about this subject using ssh-agent.Tested on a MacBook, should work pretty much the same on any Linux box.While I used GitHub for the post, this works just as well with Bitbucket, or any other Git hosting that supports SSH for that matter. ![]() ![]() Url = +refs/heads/*:refs/remotes/origin/* You can see that the repository origin is using the work the-work-repo (master) $ git remote -v Remote: Total 130 (delta 60), reused 0 (delta 0) The final step is to tell the Git client to use the new SSH keys by using the work $ git clone into 'the-work-repo'. Use the GitHub.work alias as the remote URL Add a Host entry to your SSH config file, usually under ~/.ssh/config (create it if one doesn’t already exist):Ĭopy the contents of the new SSH public key, and paste it as a new SSH key on the GitHub ~ $ cat /Users/itamar/.ssh/id_work_rsa.pub | pbcopyĪdding the new SSH key to the work GitHub account This is needed to “help” Git use the correct keys. Your public key has been saved in /Users/itamar/.ssh/id_work_rsa.pub.į6:5c:d2:d8:08:17:23:98:d1:aa:4d:1f:80:24:24:d3 key's randomart image is:Īssociate the new SSH keys with a GitHub alias Your identification has been saved in /Users/itamar/.ssh/id_work_rsa. Assuming you already have default SSH keys under ~/.ssh/id_rsa, make sure you specify a different path for the new ~ $ ssh-keygen -C public/private rsa key pair.Įnter file in which to save the key (/Users/itamar/.ssh/id_rsa): /Users/itamar/.ssh/id_work_rsaĮnter passphrase (empty for no passphrase): I managed to overcome this problem by creating new SSH keys for the work account. ![]() GitHub error message when trying to reuse SSH keys across accounts
0 Comments
Leave a Reply. |