Manual 0.8.0

Move an instance

Carry one instance to another host. An instance is one folder and the state beneath it, so moving it is a copy and a re-point.

Before you start

Read what this instance reads out of the folder it sits in:

revetly doctor --offline

[PASS] secrets   NEO4J_PASSWORD from .env

Copy the folder whole, hidden files and all:
```
cp -a . <NEW_ROOT>
```
Replace <NEW_ROOT> with the folder it moves to.

Read the chain at the new root, which REVETLY_ROOT names:

REVETLY_ROOT=<NEW_ROOT> revetly doctor --offline

[PASS] config   <NEW_ROOT> (REVETLY_ROOT)

Replay the snapshot into the new host's graph, with nothing else running yet:

docker compose run --rm revetly revetly restore <STAMP>

restored <NODES> node(s) and <EDGES> edge(s); <INDICES> index statement(s) run

Replace <STAMP> with the stamp revetly snapshot list names.

Start the stack in the folder at the new root:
```
docker compose up -d
```
You should see Container revetly-engine-<NAMESPACE> Started (as Docker Compose shows it)

Confirm the client entry reaches the engine from where it now sits:

docker compose exec revetly revetly doctor

[PASS] mcp entry   …

The ledger did not travel with the folder. Run revetly rebuild-ledger, which rebuilds it from the stamps the episodes carry at no provider cost.
A client opens the folder with nothing running under it. Start Docker, then bring the stack up in that folder.