Where Does FileRun Store Files and Metadata?
FileRun serves files from its user data directory with the database tracking shares and metadata. Back up files plus database together.
Last updated
FileRun splits content from catalog. User files sit in a data directory on disk while MariaDB or SQLite tracks shares, versions, comments, and metadata. Both halves matter for a working move.
Exact paths may vary by install method, from bare installs to Docker volumes, so read the live config before scripting. Thumbnails and previews regenerate on demand after restores. Keep cron jobs running for background indexing; stalled queues look exactly like missing files. Preview cache rebuilds itself after every restore.
Where FileRun stores this, by platform
/var/www/html/filerun/
User files plus database together per backup. Exact paths may vary by install method. Fix ownership to the web user after restores.
Frequently asked questions
How do I migrate FileRun?
Archive the user files directory with the service stopped, dump the database, and restore both to matching paths on the new host. Fix ownership to the web user afterward. Version history and shares need the database; files alone lose them.
How do I change the FileRun domain?
Edit the config for the new domain and clear caches, then verify login and sharing links. Hardcoded URLs in shares break until updated. Keep the old host read-only until the move proves clean.
Notice an outdated path? Let us know.