Commit 44ad34bb authored by Adam Hawkins's avatar Adam Hawkins

Move to drafts

parent 13bf93a3
......@@ -6,7 +6,7 @@ author: ahawkins
Development environments are a big part of every team's work. The
first time a new person joins a team they are (hopefully) pointed to
some `README` listing everyting they need to setup. This approach
some `README` listing everything they need to setup. This approach
works for small teams or teams that do not grow often. The process
does not scale for teams undergoing rapid growth or when there is not
enough time to handhold people through the setup process. Also it's
......@@ -19,7 +19,7 @@ toolchain that all engineers use on a day to day basis. Our setup is a
mix of manual unique snowflake setups and some automated bits. All
the while the company was brining in new engineers every couple of
weeks with the intent to grow the entire engineering department by 3
or 4x. It was my responsiblity to solve this problem to ensure all
or 4x. It was my responsibility to solve this problem to ensure all
members of the engineering team had access to a standardized
environment and that new team members would get going quickly.
......@@ -27,9 +27,9 @@ environment and that new team members would get going quickly.
My solution is [vagrant][] with a layer on top. Vagrant is a wonderful
tool to keep in the toolbox. VM's are a wonderful way to encapsulate
complex systems. They are easily built with automatable systems as
well. I opted to use ansible for configuration management inside the
VM. Ansible runs inside the VM so there is no need to maintain ansible
complex systems. They are easily built with automation systems. I
opted to use ansible for configuration management inside the VM.
Ansible runs inside the VM so there is no need to maintain ansible
toolchain on the host system.
Vagrant manages shared folders to make their source code (or other
......@@ -85,7 +85,7 @@ a wrapper command provides a few key benefits:
commands always targets this specific one.
* Allows layering of team specific requirements on top of
`vagrant-worktation`/`vagrant`
* Provides all users the same shorcuts and handiness without having to
* Provides all users the same shortcuts and handiness without having to
create their own shell specific changes. Users are recommended to
alias this to something short. I use `sw`.
* Create subcommands for `exec`'ing commands from anywhere.
......@@ -95,7 +95,7 @@ interesting parts. `script/host-check` runs on the host system and
verifies pre-requisites (such as `vagrant` installed, proper
environment variables set, and other things). `script/configure-guest`
handles per-user configuration that needs to happen in the VM.
`slashdeploy-workstation provision` reads all enviornment variables
`slashdeploy-workstation provision` reads all environment variables
prefixed with `SLASHDEPLOY`. These values are written to file
accessible in the VM. `script/configure-guest` sources the file, then
uses the values to do specific configuration.
......@@ -144,7 +144,7 @@ This approach has been working very well for Slashdeploy and also the
engineering department at my full time job. I encourage you consider
this approach for your team/organization.
The [source code][] for the Slashdeploy worktation is public so anyone
The [source code][] for the Slashdeploy workstation is public so anyone
can see how it works. So fork and try it out for your company. Happy
shipping!
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment