Work Machine

A work profile lives alongside your personal profile in the same repo. It can share tools and common config while overriding anything specific to your work context.

profile.env

Override variables for the work context:

profiles/work/profile.env

DOTKIT_DEV_DIR="~/work"
GITHUB_ORG=acme

These override anything set in dotkit.env for the duration of this profile’s run.

Work-specific packages

A work brew.md can install tools your personal machine doesn’t need:

# Work packages

## map

- brew install **1**
- awscli
- terraform
- kubectl

## map

- brew install --cask **1**
- zoom
- slack
- docker

Work git config

Point repos at your org and use a work email:

git/run.env

WORK_DIR=$DOTKIT_DEV_DIR
GITHUB_ORG=acme

git/config.txt

map git config --global {{key}} {{value}}
user.email = you@company.com
---
map git clone git@github.com:{{key}}/{{2}}.git $WORK_DIR/{{2}}
#acme = backend
#acme = frontend

Selecting the work profile

During bootstrap, the installer lists available profiles and prompts for selection:

Available profiles:
  1) personal
  2) work

Select a profile [number or name]: 2

Or pass it directly:

curl -fsSL dotkit.run/sh | sh -s -- --username yourname --profile work --defaults