Where Does Self-Hosted Taiga Store Uploads?
Taiga self-hosted media volume and settings paths for Docker installs, plus what to back up for a move.
Last updated
Taiga splits state across containers. Uploaded avatars and attachments live in a media volume, usually taiga-media-data, mounted at /taiga-back/media inside the backend. Postgres holds projects, users, and the references that make those files meaningful.
Settings come from a .env file next to docker-compose.yml with secrets and domain names. The backend also reads settings in taiga-back/settings. Back up the media volume, the database dump, and the env file together. Restoring only files gives you images with no projects attached.
Where Taiga stores this, by platform
taiga-media-data (/taiga-back/media in backend)
Backend mountpoint for avatars and attachments. Confirm the host volume name with docker volume ls since compose prefixes vary. Tar with the backend stopped for consistency.
.env (next to docker-compose.yml)
Holds secrets, domain, and mail settings for the compose stack. Keep a copy off the server. Rebuilding with fresh secrets logs everyone out and breaks webhooks.
Frequently asked questions
what do i back up for a Taiga migration
Back up the media volume with a Postgres dump and the .env file. Media holds avatars and attachments. The database links them to projects. One without the other leaves broken images.
how do i copy Taiga uploads off a named volume
Run docker volume ls to find the taiga-media-data volume, then mount it read only into alpine and tar it. Copy the tarball off the host. Named volumes survive compose down but they are not backups.
Notice an outdated path? Let us know.