Where Does Kbin Store Uploads and Config?
Kbin keeps uploads, config and cache in its install tree on Linux. Which folders persist and migrate.
Last updated
Kbin organizes user uploads in a public folder with config near the install root and state in its database. Federated content caches beside local uploads.
Docker is the normal deploy, so host paths depend on volume binds. Environment files decide domains and storage roots, which means two installs rarely share literal paths. Read the compose setup first on any unfamiliar box.
Where Kbin stores this, by platform
/kbin/public/uploads/
Uploads plus config and cache; database alongside per setup. Persist all three volumes. Exact internal names may vary by Kbin version, so confirm against the compose file and environment.
Frequently asked questions
Which Kbin folders must persist?
Persist uploads, config and the database volumes before first run (see the compose file). Without them, media and settings vanish on container replace. Back up the database plus uploads together as one set.
How do I migrate Kbin?
Copy uploads, config and the database to the new host with a matching Kbin version, keeping environment files alongside. Reindex after the move. Exact internal names may vary by release.
Notice an outdated path? Let us know.