Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.
If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.
This article introduces a simple way of working with Hashicorp Vault key-value secrets engine.
You should have a running Hashicorp/Vault service and Vault command available.
Here is a quick way to install a Vault dev server.
| #!/bin/bash | |
| # | |
| # A helper script to connect to a Docker for AWS manager node for running `docker` commands | |
| # | |
| # There's a few things going on here: | |
| # 1. it figures out a swarm manager's address using the AWS API | |
| # 2. it controls an SSH tunnel to Docker's API socket on that manager node, so that `docker` commands (such as `docker stack deploy`) | |
| # can be directed at that node | |
| # | |
| # Prerequisites: |
At some point you’ll find yourself in a situation where you need edit a commit message. That commit might already be pushed or not, be the most recent or burried below 10 other commits, but fear not, git has your back 🙂.
git commit --amendThis will open your $EDITOR and let you change the message. Continue with your usual git push origin master.
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
| Commit type | Emoji |
|---|---|
| Initial commit | 🎉 :tada: |
| Version tag | 🔖 :bookmark: |
| New feature | ✨ :sparkles: |
| Bugfix | 🐛 :bug: |
