Reference · the tools · templates
publish_template
What it does
Publish a saved environment as a version of its template: a clean copy that can be shared. A version takes from the saved environment only what is committed -- each project at its last commit, with no git history -- and the environment's own scripts. It leaves out the environment's personal data (bettik.json "data"), .env, the passwords Bettik made, node_modules, and anything uncommitted. It is scanned for keys, tokens, sign-ins and env files, and stopped on any. Then it is installed fresh on the release box and must answer. Versions are numbered on their own: name@r1, r2. Without go: true this only says what would happen; tell the user, and publish once they say yes. It takes a few minutes; publish_status says how it is going. A version can be shared by link, unlike a saved environment. (formerly release_snapshot)
What it needs to know
- template
- The template: "bettik-agent", or an org's, "bettik-ai/bettik-agent".
- saved · optional
- Which saved environment (its number). Omit for the newest.
- notes · optional
- What changed, for whoever installs it, in the author's words.
- go · optional
- Actually publish. Without it, only say what would happen.
Where it lands
On the box it names.