Roustem Karimov roustem

A quick note on how I'm currently handling Blue/Green or A/B deployments with Terraform and AWS EC2 Auto Scaling.

In my particular use case, I want to be able to inspect an AMI deployment manually before disabling the previous deployment.

Hopefully someone finds this useful, and if you have and feedback please leave a comment or email me.

Overview

I build my AMI's using Packer and Ansible.

WebCrypto APIs:

subtle.generateKey
subtle.exportKey
subtle.importKey
subtle.deriveBits
subtle.encrypt
subtle.decrypt
subtle.digest

	#include <stdio.h> // for fprintf, stderr, perror
	#include <stdlib.h> // for exit() and EXIT_FAILURE
	#include <errno.h> // for errno
	#include <fts.h> // for fts

	int main(int argc, const char *argv[]) {
	char * const paths[] = {"/tmp", NULL};

	FTS *tree = fts_open(paths, FTS_COMFOLLOW\|FTS_NOCHDIR, NULL);
	if (!tree) {

	#!/bin/bash -e

	echo '
	PATH=$HOME/go/bin:$PATH
	export GOPATH=$HOME
	export CDPATH=.:$HOME/src/golang.org/x:$HOME/go/src:$HOME/src/github.com:$HOME/src/github.com/nf:$HOME/src/github.com/adg
	export EDITOR=vim
	' >> ~/.profile

	sudo apt-get update

	{
	"always_show_minimap_viewport": true,
	"binary_file_patterns":
	[
	"*.d.ts"
	],
	"color_scheme": "Packages/Tomorrow Color Schemes/Tomorrow.tmTheme",
	"detect_indentation": false,
	"draw_minimap_border": true,
	"folder_exclude_patterns":

	--
	-- This example shows how bad MySQL is when handling foreign key locks.
	-- Deadlock happens when multiple transactions are inserting child records
	-- pointing to the same parent and then try to update the parent record.
	--
	-- The solution is to always try to update the parent record first
	-- but it could be hard to track the when database schema is more complex.
	--
	-- Based on: https://bugs.mysql.com/bug.php?id=48652
	--

	{
	"translate_spaces_to_tabs": true,
	"translate_tabs_to_spaces": false,
	"use_tab_stops": true
	}