Turn the watch loop on, then leave Revetly reading its sources without you.
Open the configuration page. If it is not open, run revetly config and
open the address it prints.
You should see Watch and retries.
Go to Watch and retries.
Turn on Watch loop.
Select Save.
You should see Watch loop: running on the instance card.
Read the line under the loop's state. Revetly has run the first tick by the time the page comes back.
You should see Last tick on the instance card.
The container's command is revetly supervise. With the watch loop switch on
(enabled = true under [watch]) and a positive interval, it starts one revetly watch loop
per project itself and restarts a loop that exits, with a bounded backoff.
Step 4 is the by-hand path for a switch that is off: a loop started that way is
not restarted when it exits or when the container restarts. On an instance
declaring several projects, a loop started by hand watches the default project
alone, and revetly watch --project names any other.
In revetly.toml at the project root, declare the seconds under [watch]:
# revetly.toml
[watch]
interval = 600
Read the policy this instance now declares:
revetly status
Watch: a pass every 10m …
Run one tick by hand and watch it through.
revetly watch --once
If the provider key is not set, the tick fails on the key rather than on a
source, and the key belongs in .env at the project root.
Start the loop inside the engine service:
docker compose exec -d revetly revetly watch
Read the loop back from a second shell:
docker compose exec revetly revetly status
You should see the loop is running here.
revetly watch refuses. The interval is zero, which declares unattended
reading off. Declare a positive number of seconds under [watch] in
revetly.toml.