Enter this in the search box along with your search terms:
Get all gists from the user santisbon.
Find all gists with a .yml extension.
Find all gists with HTML files.
At Gruntwork, we work with multiple software teams. That means we have to modify the "Switch Role" history multiple times. But the only way to do that today is to delete your cookie and clear all AWS Console saved settings. That got old after a while, so these instructions enable you to modify the "Switch Roles" configuration directly.
|set -euo pipefail|
|# This script will remove automatic association for all networks not listed in the whitelist|
|# passed as the first argument. Passwords will NOT be removed from the Keychain.|
|# Alternatively, you can untick "Remember networks" in Network Preferences > Wi-Fi > Advanced,|
|# but then you won't be able to auto-join networks even temporarily, and you might already|
|# have a long list to go through.|
Dumb quotes (also known as straight quotes) are straight and vertical. Proper typography never uses straight quotes. They are left over from the age of typewriters, and their only modern use is for coding.
This gist is a fork from lamont-granquist modified to be even easier and faster by taking advantage of Docker. Given the rapid development and change rate of Chef finding this gist with instructions that still are valid and reasonable was much appreciated.
This gist uses TK+Berkshelf to drive creating a vagrant virts and converging a simple recipe to install and configure NTPd. This is a simple cookbook that has one recipe, one template (for ntp.conf) and one attribute file. It works on Ubuntu 12.04/14.04 and CentOS 6.4/7.1 (and derviatives) and the attribute file is used to support both distros.
This should work on Mac (where I developed it) and any chef-supported Linux that you can get Docker onto (Ubuntu/CentOS).
Because I use ChefDK and Test Kitchen, I can largely ignore setting up Docker and Berkshelf and can get right to work on writing recipe code.
git-prebase improves on 'git rebase -i' by adding information per commit regarding which files it touched.
Add the executable to your path and git will automatically expose it as
|# YAML config for these Ansible roles:|
|# Since it's just straight config blocks, you should be able to just copy and paste what you need if you don't use|
|# those Ansible roles.|
|# End result is multiline logs combined into one, and dates are parsed correctly.|