mv ~/Downloads/mongodb-macos-x86_64-4.2.1 /usr/local/
ln -s mongodb-macos-x86_64-4.2.1 mongodb
sudo nano /etc/paths
add
mv ~/Downloads/mongodb-macos-x86_64-4.2.1 /usr/local/
ln -s mongodb-macos-x86_64-4.2.1 mongodb
sudo nano /etc/paths
add
open up Terminal and run chsh -s /bin/zsh
If interested you could go ahead and make a few basic visual changes in Profiles tab.
official repo has pretty good documentaion. The punch line is find somewhere to clone it then tell your ~/.zshrc about it. /usr/local is probably a better spot in hindsight than /etc where I put put it.
cp zshrc.zsh-template ~/; mv ~/zshrc.zsh-template ~/.zshrc
Note some of this is from memory months ago in combination with old nots so let me know if updating is needed.
::mongodump:: to backup and maintain all the BSON although not recomended for sharded clusters - see atlas documentation.
mongodump —-uri “mongodb://heroku_xxxxx:PASSWORD@ds261238.mlab.com:61238/heroku_00xzkv83”
note that for mlab the username and the authentication database are the same
I'm still not sure what but on both my systems my keys just don't get loaded back into the ssh-agent on restarts and new login sessions. I got annoyed enough at it that I jumped through the hoops of putting ssh-add into a script and writting a property list file to load as a launchagent to fix it.
If you haven't done so already you can use the well written gub hub instructions for generating ssh keys. Once you get them generated you'll add them with ssh-add -K <sshkey>
where sshkey is the file path/name. Keys are stored by default in your ~/.ssh folder
Note that you may need to use ssh-add --apple-use-keychain
in Big Sur onward instead of ssh-add -K
. I discovered the issue in Montery after skipping Big Sur.
The manual method (assuming your keys were stored into the Mac OS Keychain) is to open up Terminal