Configuration¶

Config file location¶

The default config path is:

~/.config/toolbox-dev/config.yml

Override it with the TDX_CONFIG environment variable:

export TDX_CONFIG=~/my-custom-config.yml

Config format¶

The config file is a YAML file with roles organized by category:

languages:
  python_development: true
  nodejs_development: true
  go_development: false
  rust_development: false
  cpp_development: false
  ruby_development: false
  dotnet_development: false
  zig_development: false

environments:
  fedora_packaging: false

# Optional: paths to custom Ansible task files
custom_playbooks:
  - ~/.config/toolbox-dev/playbooks/my-tools.yml

Set a role to true to enable it, false to disable it.

CLI tools¶

tdx-apply¶

Runs the Ansible playbook with your configuration:

tdx-apply              # apply config
tdx-apply -v           # verbose
tdx-apply --check      # dry run (no changes)

On first run, if no config exists, it copies the defaults and exits so you can edit them.

tdx-edit¶

Opens the config file in your $EDITOR:

tdx-edit

Creates the config from defaults if it doesn't exist yet.

tdx-upgrade¶

Upgrades the toolbox container to the latest image. See Upgrading.

Auto-apply behavior¶

A profile script (/etc/profile.d/tdx.sh) runs on every interactive shell entry and checks:

If the config file exists but has never been applied -- runs tdx-apply
If the config file is newer than the last apply timestamp -- runs tdx-apply
Otherwise -- does nothing

The timestamp is stored at ~/.config/toolbox-dev/.last-applied.

Host wrapper scripts¶

Each role installs wrapper scripts in ~/.local/bin/ for its key binaries. These wrappers let you call the tools directly from the host -- if you're inside the container, they run the binary directly; if you're on the host, they transparently execute it inside the container via toolbox run.

For example, enabling python_development creates wrappers for python3, pip3, ruff, pre-commit, pyright, and yamllint.

The container name is auto-detected from /run/.containerenv. You can override it with the TDX_CONTAINER_NAME environment variable.

Custom playbooks¶

You can run your own Ansible task files by listing them under custom_playbooks in your config. See Custom Playbooks for details.

Disabling a role¶

Setting a role to false and running tdx-apply will:

Remove the wrapper scripts from ~/.local/bin/ for that role's binaries
Not uninstall packages that were previously installed (package removal can break dependencies)