Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 0
Render Options
Leonard Ramminger edited this page Aug 22, 2026
·
1 revision
Behavior when writing to the target directory.
tempify basic_cpp my-app ...my-appis created (including nested parent paths) if it does not exist- If it exists as a file → error
- If it exists as a directory → depends on overwrite policy
| Flag | existing_path_behavior | Behavior |
|---|---|---|
| (none) | error | Target must not exist |
-f | overwrite | Target may exist; colliding files are replaced |
-s | skip | Target may exist; colliding files are left unchanged |
Config default: see Configuration.
tempify basic_cpp my-app --dry-run
tempify basic_cpp my-app --plan-jsonShows directories, files, hook paths - without filesystem changes.
Instead of a template ID, a path can be given:
tempify /path/to/template my-app --set ...When no target is given, Tempify uses output.path from template.lua (often {{ project_slug }}).
Tempify · Repository · Issues · Releases
Documentation lives in this wiki. For a build quickstart, see the README in the repository.
Prebyte (template engine) is a separate project bundled by Tempify.
- CLI Reference
- Questions & Answers
- Configuration
- Render Options
- Hooks (Users)
- Reapply & Diff
- Shared Template Store
- Prebyte Passthrough
- Shell Completion