cullylarson

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/precise64"
  config.vm.network "forwarded_port", guest: 80, host: 8080
  
  config.vm.provision "shell", path: "./vagrant-provision.sh"
  
end

cullylarson

{
    "rules": {
        "indent": [ 2, 4 ],
        "quotes": [ 2, "double" ],
        "linebreak-style": [ 2, "unix" ],
        "semi": [ 2, "never" ],
        "comma-dangle": [ 0, "always-multiline" ]
    },
    "env": {
        "es6": true,

cullylarson

"use strict"
require("babel-polyfill")

const argv = require('minimist')(process.argv.slice(2))
import gulp from 'gulp'
import gutil from 'gulp-util'
import sass from 'gulp-sass'
import concat from 'gulp-concat'
import gulpif from 'gulp-if'
import autoprefixer from 'gulp-autoprefixer'

cullylarson

import gulp from 'gulp'
import gutil from 'gulp-util'
import plumber from 'gulp-plumber'
import os from 'os'
import batch from 'gulp-batch'
import imagemin from 'gulp-imagemin'
import pngquant from 'imagemin-pngquant'
import changed from 'gulp-changed'

const plumberh = function (err) {

cullylarson

Addresses something like this:

Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   4.3.10
VBoxService inside the vm claims: 5.0.10

Option 1

cullylarson

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|
  config.vm.box = "puppetlabs/centos-6.6-64-nocm"
  config.vm.network "forwarded_port", guest: 80, host: 8080
  
  config.vm.provision "shell", path: "./vagrant-provision.sh"
  
end

cullylarson

#!/bin/bash

if [[ -z "$1" ]]; then exit 1; fi
if [[ -z "$2" ]]; then exit 1; fi

TASK=$1

# Backup folders
BK_BASE=/path/to/backup/folder
BK_DAILY=$BK_BASE/daily

cullylarson

Convenient k8s/Docker/gcloud Commands

Commands that are useful for doing stuff on Google Container Engine

Setup

$ gcloud config set project PROJECT_ID
$ gcloud config set compute/zone ZONE_NAME
$ gcloud container clusters list

cullylarson

#
# Many apps send email. In a dev environment, we generally don't want those emails
# to get out. However, we still want our app to think it's sending mail and we want
# to verify that emails are being sent, with the correct content and to the correct
# recipients.
#
# This setup solves that problem by delivering all out-bound emails to the local
# "vagrant" user's mailbox.  You can then read the emails using the "mutt" command.
#
# Most if this is copied from:

cullylarson

Pushing to a client's git repo

I'm a freelance programmer. Sometimes I work on projects where the client wants to occasionally see code updates in their own repo, but I don't want them to see my work schedule. If I push my dev repo, they'll see when I'm working, how many hours, etc. To solve that, I started maintaining a for-client branch that only shows weekly, squashed merges of master. Each commit is monolithic, with one commit message (it doesn't include all of the individual commit times, messages, etc. from the master branch).