dominicsayers

### Keybase proof

I hereby claim:

  * I am dominicsayers on github.
  * I am dominicsayers (https://keybase.io/dominicsayers) on keybase.
  * I have a public key whose fingerprint is CF56 1682 3C17 C7F2 58E0  85BC D60F 652E ADD7 362A

To claim this, I am signing this object:

dominicsayers

# At the end of .bashrc
dev () {
  cd "$HOME/Development/$1"
}

dominicsayers

Verifying that +dominicsayers is my openname (Bitcoin username). https://onename.com/dominicsayers

dominicsayers

module Registerable
  extend ActiveSupport::Concern

  module ClassMethods
    # Register a new record or return an existing one. This version will work
    # in a highly-concurrent environment where multiple process are updating
    # this model, but it's slower than `fast_register`.
    def safe_register(attributes = {})
      begin
        create! unique_values(attributes)

dominicsayers

Removing all secrets from the repo

1. Deployment to production is from CircleCI.
2. The deployment command is configured in circle.yml, which is checked into the repo and cannot contain any secrets.
3. CircleCI can have env vars configured
4. circle.yml is passed through ERB [check], so we can add secret parameters to the deployment command using erb, e.g. foreplay deploy production -u <%= ENV['DEPLOYMENT_USERNAME'] %> -p <%= ENV['DEPLOYMENT_PASSWORD'] %>
5. The secret credentials can be used to connect to a remote service and download the remainder of the production secrets.
6. The secrets can be included in the .env file created by Foreplay and become part of the production runtime environment.

dominicsayers

{
  "headers": {
    "Received": [
      "by lbio15 with SMTP id o15so1647431lbi.1 for <smartangel@xenapto.me>; Sat, 06 Jun 2015 08:19:30 -0700",
      "by 10.112.72.99 with HTTP; Sat, 06 Jun 2015 08:19:30 -0700"
    ],
    "Date": "Sat, 06 Jun 2015 16:19:30 +0100",
    "From": "Dominic Sayers <dominic.sayers@gmail.com>",
    "To": "To1 <to1@xenapto.com>, To2 <to2@xenapto.com>",
    "Cc": "Cc1 <cc1@xenapto.com>, Cc2 <cc2@xenapto.com>",

dominicsayers

{
  "headers": {
    "Return-Path": "dominic@xenapto.com",
    "Received": [
      "by wibut5 with SMTP id ut5so50815534wib.1 for <smartangel@xenapto.me>; Sat, 06 Jun 2015 14:31:21 -0700",
      "from [192.168.1.75] (host86-150-30-216.range86-150.btcentralplus.com. [86.150.30.216]) by mx.google.com with ESMTPSA id q4sm16773563wju.14.2015.06.06.14.31.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Jun 2015 14:31:20 -0700"
    ],
    "Date": "Sat, 06 Jun 2015 22:31:18 +0100",
    "From": "Dominic Sayers <dominic@xenapto.com>",
    "To": "To1 <to1@xenapto.com>, To2 <to2@xenapto.com>",

dominicsayers

{
    // The number of spaces a tab is considered equal to
    "tab_size": 2,

    // Set to true to insert spaces when tab is pressed
    "translate_tabs_to_spaces": true,

    // Set to true to removing trailing white space on save
    "trim_trailing_white_space_on_save": true,

dominicsayers

1. I installed BIND during the Ubuntu setup process by selecting DNS Server when asked for package selections.
2. Click Create Master Zone
3. Enter al.gy for Domain Name/Network and click Create
4. Add A-records
5. Apply Zone
6. Apply configuration

dominicsayers

Cloning an Ubuntu guest on Virtualbox

Cloning a VM is easy in theory but if you don't set up networking properly in the newly cloned machine it can kill all networking on the host.

In particular, Virtualbox gives your cloned machine a new NIC with a new MAC code. This is probably what you want since you don't want multiple machines on your network with the same MAC address. But Ubuntu still has the NIC from the original machine in one of its configuration files, so there's a clash between the hardware created by Virtualbox and the Ubuntu VM's own view of the world.*

Simple but tedious to fix. Here goes, on the Virtualbox host machine:

1. su vbox
2. VBoxManage clonevm original_vm_name --name new_vm_name --register