It is rather common that companies have scripts to get their developer machines up and running. Many of us also create our own version to have our ...
For further actions, you may consider blocking this person and/or reporting abuse
I've been doing this for a while with github.com/caseywebb/laptop, and it makes setting up a new machine painless. I've got it set up to auto update whenever my .zshrc is ran which works well considering I've usually got to run
refreshenvto get new bins in the PATH.I also use keybase to sync my ssh and gpg keys across machines, so after running this script I'm pretty much set to go.
Nice setup!
I like the way you run the scripts right from your
.zshrcand how you useLAST_EPOCH. I imagine it could be a little surprising if you open a new terminal and it suddenly starts to update..Also, do you have any issues with the loading time when opening a new terminal? I try keeping my changes as minimal as possible since I open new terminals quite a bit and I like it to be as quick as possible.
The naming scheme is such that the 3X-X.sh scripts are spawned in separate windows, so they don't affect the startup time at all.
That being said, I do have a small delay, but I like the tradeoffs.
1) I store my keys and credentials in Keybase, and symlink them to my local file system. It not only makes syncing across machines easier, but if I need to revoke a machine, I just revoke its keybase access.
2) The second thing is that I make a curl to
api.github.com/zen. This is my uber simple way of knowing if I have internet access or not when I open the shell, considering it is where I spend most of my time.Cool, missed that part about running the
3Xscripts in the background. That helps for sure. Only have to make sure that they don't prompt for any user input and don't throw any errors I guess.The syncing setup is nice too.
Thanks for sharing!
Nice. I implemented something similar a while ago at a previous job. We had separate install (designed to run once) and update (run frequently) commands that made it a pain to add new software to existing machines without bugging people to run install tasks manually.
I took the idea a step further in our case - converting our shell scripts into a bunch of individual task classes in Python that defined dependencies so non-dependent tasks could be run in parallel. Quite a fun exercise!
I really like the simplicity of having a single file. But I also understand that not everyone has the luxury of keeping the setup so minimal. For a certain size it definitely reasonable to split things up and eventually switch to a language that is easier to reason with.
As we're sharing, I use something simple aliased to a command:
alias update='brew update && brew upgrade && brew cleanup && apm upgrade && mas upgrade'
Adding in Atom package manager and github.com/mas-cli/mas
Going to add some of your ideas too :)
A significant amount of this logic can be replaced directly by
brew bundle: github.com/Homebrew/homebrew-bundleSpecifically
brew bundle --globalandbrew bundle cleanup --global.Nice! homebrew-bundle definitely looks like a good alternative for more complicated setups. I still like the simplicity and flexibility of managing it myself since my setup is so minimal anyways.
RC file management - rcm (github.com/thoughtbot/rcm) with post-up/pre-up script?
Works on macOS with homebrew.