Environment Variables
Set by the bootstrap installer
Section titled “Set by the bootstrap installer”DOTKIT_DIR is written to ~/.local/share/dotkit/export.env after a successful bootstrap.
| Variable | Description |
|---|---|
DOTKIT_DIR | Absolute path to your cloned dotkit repo (e.g. ~/dotkit). |
Set during dotkit apply
Section titled “Set during dotkit apply”Available to all .txt, .md, and .sh files running inside a profile.
| Variable | Description |
|---|---|
DOTKIT_PROFILE | Name of the active profile (e.g. personal). |
DOTKIT_PROFILE_DIR | Absolute path to the active profile directory ($DOTKIT_DIR/profiles/$DOTKIT_PROFILE). |
Set during script execution
Section titled “Set during script execution”Available to all .txt, .md, and .sh files run by dotkit apply or dotkit run.
| Variable | Description |
|---|---|
DOTKIT_FUNCS | Path to the dotkit_funcs file. Scripts source this to get dotkit map, dotkit install, dotkit ask as shell functions. Set automatically by dotkit run and dotkit apply. |
Used by the CLI
Section titled “Used by the CLI”| Variable | Description |
|---|---|
DOTKIT_PAT | GitHub personal access token. Used by dotkit run for private repos and by the bootstrap installer for private repo cloning. |
Source of truth
Section titled “Source of truth”DOTKIT_DIR is persisted to ~/.local/share/dotkit/export.env. The active profile is stored separately in ~/.local/share/dotkit/active and used by dotkit add to resolve DOTKIT_PROFILE_DIR.
Overriding at runtime
Section titled “Overriding at runtime”Any variable can be overridden inline:
DOTKIT_PROFILE_DIR=~/dotkit/profiles/work dotkit apply ~/dotkit/profiles/work