Boxen: How to Manage an Army of Laptops and Live to Talk About It

developing software is
harder than it used to be

our toolchains have gotten
more robust

our toolchains have gotten
more complicated

better install a ruby version
manager, like 8 versions of ruby, a
handful of gems to try and make
the behavior remotely sane, and
then pray it doesn't break

s/ruby/literally everything but
bash/g

friction
is anything that
gets in the way of doing stuﬀ

friction
is the greatest source of
frustration in every organization

conﬁguring development
environments is a week-long
marathon in friction

"all right, new work laptop! i
wonder where that blog post i
used last time to set up ruby,
python, go, and git is. hopefully it
still works and by the end of the
week i can start shipping."

e
"all right, new work laptop! i

m
wonder where that blog post i

a
used last time to set up ruby,

l
python, go, and git is. hopefully it
still works and by the end of the
week i can start shipping."

getting any part of the stack
running locally should never block
someone from shipping

when was the last time you knew
every human was running the
same services in dev and prod?

"hey so my postgresql isn't
working. is yours working? it is?
huh. i have no idea what's wrong."

m e
"hey so my postgresql isn't

a
l
working. is yours working? it is?
huh. i have no idea what's wrong."

manual audits are
error-prone

ask software instead of humans

lock every core component to the
same version as in prod

"jeeeeeez the mac app store has
been bugging me for like forever! i
have a billion updates... meh"

m e
"jeeeeeez the mac app store has

a
l
been bugging me for like forever! i
have a billion updates... meh"

maybe you use CM in dev already,
but when was the last time
you updated and ran it?

security is a war of attrition

bug people enough about security
and they stop caring about it

"ugh, another security thing?
whatever, i have way more
important things to do"

m e
"ugh, another security thing?

a
l
whatever, i have way more
important things to do"

let code handle security,
then inform people so they know
why the code's making changes

BOXEN ENABLES YOU TO
MAKE THESE THINGS
BETTER FOR YOUR ORG

it checks for prerequisites and
conﬂicts before each run

it detects certain changes post-run

homebrew, git, hub, gcc, rbenv,
ruby 1.8.7, ruby 1.9.3, ruby 2.0.0,
nvm, nodejs 0.4.x, nodejs 0.6.x,
nodejs 0.8.x, nginx, .dev dns, FDE,
and puppetlabs-stdlib

rbenv_gem, repository, osx_chsh,
osx_login_item, boxen::project,
ruby::local, mysql::database, etc.

package: homebrew,
compressed_app

gem that simpliﬁes creating new
puppet modules, optimized for the
boxen-recommended stack

librarian-puppet, rspec-puppet,
puppet-lint, etc.

example module using cardboard

small rails app to allow distributing
your boxen easily, with auth

$ boxen --projects

# list projects Boxen knows about

$ boxen <project>

# run it but include <project> in the
catalog automatically

# modules/projects/manifests/team.pp

class projects::team {
boxen::project { 'team':
dotenv => true,
mysql => true,
nginx => true,
ruby => '1.9.3',
source => 'github/team',
}
}

$ boxen team

warning: Setting up 'team'. This can
be made permanent by having 'include
projects::team' in your personal
manifest.

cloned repo

nginx vhost

ruby version

mysql databases

.env ﬁle

$ cd ~/src/team
$ script/server
$ open http://team.dev/

i want to install $x but only for me

# modules/people/manifests/wfarr.pp

class people::wfarr {
include minecraft
}


include zsh
}


case $::hostname {
'bender': {
include projects::all
}

'scruffy': {
include projects::team
}

default: {}
}
}


  git::config::global {
    'alias.st': value => 'status';
    'alias.ci': value => 'commit';
    'alias.di': value => 'diff';
    'alias.lp': value => 'log -p';
    'color.ui': value => 'true';
    'user.name':
value => 'Will Farrington';
    'user.email':
value => 'wfarr@github.com';
  }
}


include osx::example_things
}

$ boxen
Error: ZOMG at /opt/boxen/repo/
modules/people/manifests/wfarr.pp:8
on node scruffy.gateway.github.lan

Sorry! Creating an issue on github/
totally-a-madeup-repo-name.

i ﬁx the error and run `boxen`

# config/boxen.rb

ENV['BOXEN_REPO_NAME'] =
'github/boxen'

ENV['BOXEN_ISSUES_ENABLED'] = 'yes'

$ boxen

Boxen has a dirty tree, won't auto-
update!

$ boxen

Boxen has unpushed commits on
master, won't auto-update!

$ boxen

Boxen on a non-master branch 'new-
project', won't auto-update!

"So, we're uh in the air. We made
it. That's uh good news,
obviously."

"Flight attendants, if you could
just hang on to uh... whatever..."

 wfarr
come work with me on
things like boxen

speakerdeck.com/wfarr/
boxen-puppetcamp-atl

Boxen: How to Manage an Army of Laptops and Live to Talk About It

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Boxen: How to Manage an Army of Laptops and Live to Talk About It

Similaire à Boxen: How to Manage an Army of Laptops and Live to Talk About It (20)

Plus de Puppet

Plus de Puppet (20)

Dernier

Dernier (20)

Boxen: How to Manage an Army of Laptops and Live to Talk About It