Legacy migration

Rebuild matrix.meshly.chat as a private test node, not a public onboarding path.

If the current server was only used for trials, the cleanest route is to recreate it with token registration enabled and /_synapse/admin exposed.

Option 1. Recreate the server cleanly

If the node only held test data, delete the stack, redeploy it with the new installer, and keep the resulting token for internal testing only.

Option 2. Migrate the current server in place

Make these minimum changes:

enable_registration: true
enable_registration_without_verification: false
registration_requires_token: true

Update homeserver.yaml with the values above.
Expose /_synapse/admin in your reverse proxy alongside /_matrix and /_synapse/client.
Restart Synapse.
Log in with the admin account and create a registration token through the Synapse admin API.
Disable any remaining public-open registration behaviour.

Quick validation commands

curl https://matrix.meshly.chat/_matrix/client/versions
curl https://matrix.meshly.chat:8448/_matrix/federation/v1/version
curl https://matrix.meshly.chat/_synapse/admin/v1/server_version

After migration

Use the generated token only for internal testing.
Do not present matrix.meshly.chat as the default homeserver in the app.
Rotate the token immediately if it leaks.