Create an instance with revetly init

Scaffold revetly.toml, the compose file and AGENTS.md into a folder. Nothing is billed and no container is started.

Before you start

• Install Revetly from the handout and start the stack
• Stand in a folder you want read, git repository or not.

Configuration page

Command line

1. Scaffold the instance into the folder you are standing in:

   revetly init
   

   commit what init wrote (revetly.toml, docker-compose.yml, AGENTS.md) …
   

   If the folder held no commit, init makes the first one and says that in place of the line above.

2. Add the update endpoint on a re-run:

   revetly init --transport container --image revetly:0.8.0 --updater
   

   appended revetly.toml (+[updater] — kept what was there)
   

3. Scaffold an instance that declares no provider:

   revetly init --lite
   

   Revetly asks for a provider key on a full instance and for none on a lite one.

Troubleshooting

• A re-run kept what it found and applied none of your flags. An existing revetly.toml is never rewritten. Edit the file, or scaffold into a folder that holds none.
• The re-run left two compose files. The folder already held a docker-compose.yml, so the container stack landed in revetly-compose.yml. Every command Revetly writes names that file.

Next steps

• Give an instance a provider key and confirm it
• Run an instance with no provider key