This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
require 'rake' | |
require 'rspec/core/rake_task' | |
require 'yaml' | |
require 'highline/import' | |
properties = YAML.load_file('properties.yaml') | |
ENV['SSH_USER'] = ask("Enter ssh user: ") { |q| q.echo = true } | |
ENV['SSH_PASSWORD'] = ask("Enter ssh password: ") { |q| q.echo = false } |
# This gist is compatible with Ansible 1.x . | |
# For Ansible 2.x , please check out: | |
# - https://gist.github.com/dmsimard/cd706de198c85a8255f6 | |
# - https://github.com/n0ts/ansible-human_log | |
# This program is free software: you can redistribute it and/or modify | |
# it under the terms of the GNU General Public License as published by | |
# the Free Software Foundation, either version 3 of the License, or | |
# (at your option) any later version. | |
# |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars
file, reference that vars
file from your task
, and encrypt the whole vars
file using ansible-vault encrypt
.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
# rubocop v0.35.0 から inherit_gem という機能が増えたので gem にしました | |
# https://github.com/onk/onkcop | |
inherit_gem: | |
onkcop: "config/rubocop.yml" |
#!/bin/bash | |
# | |
# slack notifier on shell (specified channel) | |
# @asmz | |
# | |
# Usage | |
# ./slack_notifier.sh [channel_name] | |
# | |
# Configuration | |
# Required SLACK_API_TOKEN environment variable before open tmux. |
This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.
Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,
/* | |
Helpers for setting position using padding and margin | |
*/ | |
.p-0 { | |
padding: 0px; | |
} | |
.p-3 { | |
padding: 3px; |