Migration

Migration help

It is possible to use the same database as used by filebrowser/filebrowser, but you will need to follow the following process:

1. Create a configuration file according to configuration wiki.
2. Copy (save backup!!) your database file from the original filebrowser to the path of the new one.
3. Update the configuration file server.database to point to the database file.
4. If you are using docker, update the docker-compose file or docker run command to use the config file as described in the install section above.
5. If you are not using docker, just make sure you run filebrowser -c config.yaml and have a valid filebrowser config.

Note

If you see a fatal error creating tmp directory, that means the user executing the binary doesn't have permission to create directories in the filesystem. The OG filebrowser allows for no cache dir, but this version mandates a cache directory -- to ensure archive creation occurs on disk rather than in memory (can easily crash the server otherwise)

Things that won't work on successful migration

• share links (need to be re-created)
• branding (needs to be re-created)
• theme (needs to be re-created)
• Rules
• Runners

The filebrowser Quantum application should run with the same users you have from the original. But keep in mind the differences that may not work the same way, but all user configuration should be available.

Migrating back to original

You cannot migrate back. Make sure you have a backup.