- Create new Ubuntu Micro instance (e.g., Name = Tools)
- Stop instance you want to lower EBS volume.
- Create AMI image as backup of your instance.
- Create an empty X GB Amazon EBS volume in the same availability zone where X is smaller size you desire.
- Detach the volume you wish to resize from the stopped instance from step 2 above.
- Attach the original volume to the Tools instance (e.g., as /dev/xvdf)
- Attach new downsized volume to the Tools instance (e.g., as /dev/xvdg)
Install ODBC Manager: | |
http://www.odbcmanager.net/ | |
?? Not sure if below is needed | |
$ brew install libiodbc | |
Install the following libraries: |
import re | |
import boto3 | |
import csv | |
from botocore.exceptions import ClientError | |
ec2 = boto3.client('ec2') | |
def get_snapshots(): | |
return ec2.describe_snapshots(OwnerIds=['self'])['Snapshots'] |
To allow for diffing filesystems via rsync or running diff commands local vs remote. To make this work, easiest to allow root user to ssh into AWS instance.
For each machine you want to issue distributed compare like rsync or run diff remotely to any file:
sudo su
cd ~/.ssh
mv authorized_keys authorized_keys.orig
ssh-keygen -y -f somekey.pem > somekey.pub
TL;DR: To avoid breaking the build when merging independent PRs to master, introduce a "demilitarized zone" branch, merge PRs to it and merge it to master automatically on successful builds.
I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.
- Two developers working on independent features must never be blocked by each other
- No code freeze! Ever! For any reason!
- A developer must be able to base derivative work on another developer's work, without waiting for any third party
- Two developers working on inter-dependent features (