Where Does OneDev Store Repos and Data?
OneDev keeps everything under its install dir, usually opt onedev. Back up that tree plus external DB if configured.
Last updated
OneDev is unusually self contained for a code platform. Repos, databases, indexes, logs, and temp files all live under the install directory, defaulting to opt onedev on Linux and a matching path in containers. External databases are optional, not required.
That makes backup one archive of the tree with the service stopped. Volume mounts in Docker installs point at the same internal path. Build workspaces nest under the tree and clean on schedule. Upgrades replace code in place while data stays put.
Where OneDev stores this, by platform
/opt/onedev
Repos, embedded DB, indexes, and logs. The whole backup unit when using the built in database.
/opt/onedev/conf/wrapper.conf
Server config and launcher state inside the tree. survives upgrades in place. Check here when ports or memory need tuning.
Frequently asked questions
How do I back up OneDev?
Archive the install dir with the service stopped, plus a dump if using external Postgres. Built in backups from the UI cover the same set.
Does OneDev need the Docker socket?
Mount host Docker socket into the OneDev container. Job runners need it for builds. Data stays in the install dir regardless.
Notice an outdated path? Let us know.