I'm going to cover a simple, but effective, utility for managing state and transitions (aka workflow). We often need to store the state (status) of a model and it should only be in one state at a time.
| Vagrant.configure("2") do |config| | |
| config.vm.box = "dummy" | |
| config.vm.provider :aws do |aws, override| | |
| override.ssh.username = "ubuntu" | |
| override.ssh.private_key_path = "/path/to/ssh/key" | |
| override.vm.box_url = "https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box" |
| # alias to edit commit messages without using rebase interactive | |
| # example: git reword commithash message | |
| reword = "!f() {\n GIT_SEQUENCE_EDITOR=\"sed -i 1s/^pick/reword/\" GIT_EDITOR=\"printf \\\"%s\\n\\\" \\\"$2\\\" >\" git rebase -i \"$1^\";\n git push -f;\n}; f" | |
| # aliases to change a git repo from private to public, and public to private using gh-cli | |
| alias gitpublic="gh repo edit --accept-visibility-change-consequences --visibility public" | |
| alias gitprivate="gh repo edit --accept-visibility-change-consequences --visibility private" | |
| # delete all your repos using gh-cli (please do not run this unless you want to delete all your repos) | |
| gh repo list --limit 300 --json url -q '.[].url' | xargs -n1 gh repo delete --yes |
A Pen by A Non Ymous on CodePen.
SSHPass is a tiny utility, which allows you to provide the ssh password without using the prompt. This will very helpful for scripting. SSHPass is not good to use in multi-user environment. If you use SSHPass on your development machine, it don't do anything evil.
apt-get install sshpass
This should get rid of the rvm dir and any installed rubies:
$ rvm implode
| package main | |
| import ( | |
| "compress/gzip" | |
| "fmt" | |
| "io" | |
| "os" | |
| "strconv" | |
| "time" | |
| ) |
If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.
Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.
The simplest way to add an alias for a specific git command is to use a standard bash alias.
# .bashrc
Now located at https://github.com/JeffPaine/beautiful_idiomatic_python.
Github gists don't support Pull Requests or any notifications, which made it impossible for me to maintain this (surprisingly popular) gist with fixes, respond to comments and so on. In the interest of maintaining the quality of this resource for others, I've moved it to a proper repo. Cheers!