Where Does Pijul Store Its Config File?
Pijul reads global config from ~/.config/pijul/config.toml on Linux (~/Library/Application Support/pijul and %APPDATA%\pijul elsewhere).
Last updated
Pijul config is a config.toml resolved per OS convention. Linux checks ~/.config/pijul first. macOS uses ~/Library/Application Support/pijul. Windows uses %APPDATA%\pijul. Fallbacks exist ($HOME/.config/pijul, then $HOME/.pijulconfig), but a standard install writes to the conventional spot.
Keep global identity in that file and per-repo details in .pijul/config inside each checkout. The repo file takes precedence, which keeps machine-specific values out of your global config when you sync dotfiles.
Where Pijul stores this, by platform
~/.config/pijul/config.toml
The dirs-based default on Linux. pijul picks this up automatically; create the pijul subdirectory and config.toml inside it.
~/Library/Application Support/pijul/config.toml
Same filename, macOS convention directory. Reach it with Go > Go to Folder in Finder.
%APPDATA%\pijul\config.toml
Paste %APPDATA%\pijul into Explorer. $PIJUL_CONFIG_DIR beats all of these when set.
Frequently asked questions
Can I override where Pijul looks for config?
Set PIJUL_CONFIG_DIR to the directory holding your config.toml. Pijul checks that first, before any platform default, which makes per-project or portable setups trivial.
Where does repo-specific Pijul config live?
Edit .pijul/config at the repo root. Repo settings win over global ones, so identity, remotes and hooks that differ per project belong there rather than in your global file.
Notice an outdated path? Let us know.