Where Does Tuleap Store Data and Config?
Tuleap keeps everything in /data (or /srv/tuleap) with credentials in .env. Database, repos, and docs travel as one tree.
Last updated
Tuleap concentrates state in one tree: /data (or /srv/tuleap) holds the database, git repositories, documents, and configuration together, deliberately easing migration and disaster recovery. Credentials and domain wiring arrive via .env (FQDN, DB passwords, admin password). Docker needs a dedicated MySQL 8.4 plus Redis; shared database servers are refused by design.
That single-tree design is the backup: copy the folder and you hold code plus data plus config, unlike split apps. Admin passwords surface from container files on first boot; record them then. Upgrades pull images and rerun against the same tree. Filesystem mounts beat named volumes here precisely because the tree is meant to move as one.
Where Tuleap stores this, by platform
/data (Docker mount)
Database, repos, documents, config as one tree. Mount the folder (not anonymous volumes) for movable backups. Dedicated MySQL required; shared servers refused. Credentials in .env beside it.
Frequently asked questions
how do i back up tuleap
Copy the whole data tree (/data or /srv/tuleap) plus .env with containers stopped. Database, git repos, documents, and config travel as one filesystem unit by design. Restore to the identical mount path; internal references assume it.
can tuleap share a mysql server
Only with a dedicated database and filesystem mount, never a shared one. Tuleap demands specific SQL modes and quality of service the shared hosts cannot promise, and consistent backups get nearly impossible. The docs refuse shared setups explicitly.
Notice an outdated path? Let us know.