Uninstalling
Stop it, keep a last backup if anyone might want their data back, then remove the containers and, only if you are sure, the volumes with every message and file.
Tell your crew first
Members can export their own data under Settings > Account & security as long as the server runs. Give them time, and take one last backup for yourself.
Stop and remove the containers
In the deployment folder:
docker compose --profile autoupdate --profile turn down
This stops and removes the containers and the networks, including the optional updater and coturn services. Your data stays in the Docker volumes, and starting again later with docker compose up -d brings everything back.
Delete the data for good
docker compose --profile autoupdate --profile turn down -v --rmi allcd .. && rm -r mnema-talk
-v also removes the named volumes postgres18-data, seaweedfs-data and the old postgres-data; --rmi all removes the images the stack used. The last line deletes the folder.
The folder holds .env with every secret. Delete old backups the same way once nobody needs them.
Clean up around it
- The reverse proxy: remove the entry for
chat.example.com(Caddyfile, DSM reverse proxy, Nginx Proxy Manager). - The router and firewalls: remove the forwards and rules for 443, 80, 50000–50050 and 3479.
- DNS: delete the A record, or point it somewhere else.
- Cron: remove the nightly backup job.
- Desktop apps: members remove the server from the rail, which also wipes its stored session and local data from their device.