dotkit.env
dotkit.env
Section titled “dotkit.env”Sits at the repo root. Sourced before any profile runs.
Any key set here is exported to all scripts in all profiles (via set -a). Put your own custom variables here, like DOTKIT_DEV_DIR for a shared dev folder path.
Example
Section titled “Example”# dotkit.envDOTKIT_DEV_DIR="~/dev"profile.env
Section titled “profile.env”Sits at the profile root (profiles/<name>/profile.env). Sourced after dotkit.env. Can override any variable.
Example
Section titled “Example”DOTKIT_DEV_DIR="~/work"GITHUB_ORG=acmerun.env
Section titled “run.env”Sits inside a run folder. Sourced before executing that folder’s files. Scoped to that folder only.
Example
Section titled “Example”MY_DEV_DIR=$DOTKIT_DEV_DIRGITHUB_USER=yournamelink.env
Section titled “link.env”Marks a folder as a link folder. Read by dotkit link.
| Key | Description |
|---|---|
DEST | Destination directory for symlinks. Absolute, ~/path, or relative to link.env. |
Example
Section titled “Example”DEST=~todo.env
Section titled “todo.env”Marks a folder as a todo folder. Read by dotkit todo.
| Key | Description |
|---|---|
DEST | Output directory or full .md path. Relative to todo.env. |
NAME | Output filename. Default: TODO.md. |
TITLE | H1 heading in the output. Default: folder name. |
Example
Section titled “Example”DEST=..NAME=MANUAL.mdTITLE=Setup Checklist