Tern keeps everything for a project under
.tern/ in its root, and finds it from any subdirectory by
walking up.
.tern/
├── config.toml Templates and their overrides (committed)
├── converters/ Installed Lua converters, one directory per template (committed)
├── data/ Installed template data, one directory per template (committed)
├── cache/ Git clones of the templates (ignored by its own .gitignore)
├── store.db SQLite store, plus its -shm and -wal files (ignored)
├── pipelines.toml Pipelines generated for local profiles, when there are any
└── .gitignore Generated by tern: ignores store.db and its WAL files
config.toml is the source of truth. tern -u
rebuilds the store, the installed converters and data from it, so a
fresh clone needs only tern -u before its first
tern. The installed converters/ and
data/ are committed so the exact files a build used stay
visible in history.
Converters shared across projects can live in
converters/ under the user data directory,
~/.local/share/tern/ on Linux (reference Converters).