eleven / messenger Public

Docs: a plain 'miren deploy' preserves the disk — never 'app delete' to update

The data loss across this session was from running 'miren app delete' before
redeploying; a normal deploy preserves SQLite (messages, invites, push subs,
VAPID, group name). Verified on the test instance across two plain redeploys.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Paul Campbell 4 months ago f05053ec92d6cffef5b80b5d41fb9e1d5499049a parent 3d11be8

1 file changed, +9 −0

README.md +9 −0

diff --git a/README.md b/README.md

index 4fc5f83..2d027d4 100644

--- a/README.md

+++ b/README.md

@@ -101,6 +101,15 @@ Then point DNS for `group.luan.chat` at the cluster (a CNAME to the

`*.miren.systems` hostname Miren prints, or an A record to the server IP). Once

DNS resolves, Miren provisions TLS automatically.

+**Updating later (no data loss):** just run `miren deploy` again — a normal deploy

+**preserves the disk**, so SQLite (messages, invites, push subscriptions, VAPID

+keys, group name) all survive. **Do not `miren app delete` to update** — that

+deletes the disk and wipes everything; use it only to intentionally reset.

+**More instances from one repo:** `./deploy-instance.sh <name> <name>.luan.chat`

+gives each its own app + disk + token + route (re-run it to update an instance;

+it preserves that instance's data too).

Your admin URL is then:

```