GitHub

File Locations

Where lct stores its files.


Derived paths at a glance

LCT expands the base directories (see Environment Variables) into specific working paths:

Path Default Contents
LCT_CONFIG_DIR $CONFIG_DIR/lct Root for user config files.
LCT_CONFIG_FILE $CONFIG_DIR/lct/config.yaml Main configuration contract read by all commands.
LCT_SHARE_DIR $SHARE_DIR/lct Shared data root used for bootstrapping.
LCT_REMOTE_DIR $SHARE_DIR/lct/remote Staging area populated by lct gather; push this to your repo.
LCT_REMOTE_SECRETS_DIR $SHARE_DIR/lct/remote/secrets Encrypted secrets collected during lct gather.
LCT_ENV_FILE $SHARE_DIR/lct/env.yaml Environment variable store used by lct env and lct reload.
LCT_ALIAS_FILE $SHARE_DIR/lct/alias.yaml Alias definitions surfaced by lct reload.
LCT_BREW_FILE $SHARE_DIR/lct/Brewfile Brew bundle created during lct gather.
LCT_PLUGINS_DIR $SHARE_DIR/lct/plugins Installed plugin payloads.
LCT_PLUGINS_CACHE_DIR $CACHE_DIR/lct/plugins Download cache for plugins.
LCT_MODULES_DIR $SHARE_DIR/lct/modules Installed modules.
LCT_MODULES_BIN_DIR $SHARE_DIR/lct/modules/bin Symlinked module executables added to PATH.
LCT_MODULES_CACHE_DIR $CACHE_DIR/lct/modules Download/build cache for modules.
LCT_STATE_DIR $STATE_DIR/lct State files and logs.
LCT_DEBUG_LOG_FILE $STATE_DIR/lct/debug.log Verbose log file when --verbose is used.

Practical tips

  • The remote directory (LCT_REMOTE_DIR) is safe to version control; secrets are encrypted under remote/secrets.
  • Cache directories can be removed safely; they will be recreated on demand.
  • If you relocate SHARE_DIR or CACHE_DIR, ensure your shell profile (lct setup) points to the same values to keep paths consistent.