Where Does Self-Hosted Remotely Store Data?
Remotely keeps Remotely.db plus logs in /app/AppData, mounted to /var/www/remotely. Env selects the database provider.
Last updated
Remotely splits into volume and env. The /app/AppData volume (host /var/www/remotely by convention) holds Remotely.db (SQLite default) plus server logs, persisting across recreates. Database provider and connection strings arrive as Remotely_* environment variables; everything else configures through the web Server Config page after login.
Upgrades from bare installs mean overwriting the old db file into the volume before first boot. Reverse-proxy with Caddy for internet exposure; first run registers the admin account in-app. Logs beside the database make the same folder the debugging target when sessions fail to connect.
Where Remotely stores this, by platform
/app/AppData (Docker volume)
Remotely.db plus server logs. Host convention /var/www/remotely. Env selects SQLite/SQLServer/Postgres provider. Bare-install upgrades overwrite the old db here first.
Frequently asked questions
how do i back up remotely
Copy the /app/AppData folder (Remotely.db plus logs) with the container stopped, plus your env/compose record. Devices, scripts, and users travel in the db. Restore to the same mount; SQLServer/PG users dump those instead.
can remotely use postgres instead of sqlite
Set Remotely_ApplicationOptions__DbProvider plus the matching connection string (SQLite/SQLServer/PostgreSQL). Default SQLite writes Remotely.db into AppData. Server-side settings beyond that live in the web Server Config page, not files.
Notice an outdated path? Let us know.