Skip to content
KylthDOCS

Uninstall

Take your projects with you, stop Kylth, and understand what stays on the server.

Before you uninstall

To move a project somewhere else, take a Portable export first. It’s in the project’s Backups tab: select Export now. The export contains:

  • supabase/migrations/: the project’s migrations as a Supabase CLI migrations folder. supabase db push can apply them to Supabase Cloud or another self-hosted Supabase.
  • schema-snapshot.sql: the current schema, as plain SQL.
  • data.dump: the data, from pg_dump.
  • README.txt, which explains how to use them.

Kylth’s regular backups can only be restored by Kylth. Portable exports are the format for leaving.

Stop Kylth

cd /etc/kylth && docker compose down
docker rm -f kylth-caddy

This stops Kylth and removes its Caddy.

What happens to your projects

  • Their containers keep running, but they’re no longer reachable at their addresses, because Caddy served those. They’re still reachable from the server itself.
  • These folders stay on the server until you remove them: /opt/kylth, /opt/supabase-projects, /opt/kylth-backups and /etc/kylth.
  • There’s nothing to deactivate. The licence is checked offline, so no server holds a record of your install.

Remove the folders only once you’re sure you don’t need them. Stop the projects’ containers with Docker first, and keep a copy of anything you want, as described in Backups.