Storing Config Database in Unfetter

Unfetter Discover relies on configuration files, SSL certs, and a Mongo Database for operating. In 0.3.6 and earlier, this data was running inside the Docker Containers.

However, in version 0.3.7, we moved to using Named Docker Volumes to easily manage volatile or deployment specific data. Docker Images should never change themselves and be able to restart and be recreated at will. This volatile data is necessary for the application to manage configurations and keep user created data.

There are 4 named volumes:

• mongo-db - Holds the data from the MongoDB instance
• ui-config - Tells the UI which OAuth system to use (GitHub or GitLab)
• certs - The SSL certificates the server needs for HTTPS access to Unfetter Discover
• private-config - A volume that holds the private-config.json file, which tells Unfetter how to use the User Authentication service.

In hosts.ini, there is a Backup directory. This is a local directory in which the Ansible Playbook, task-backup-vol-container.yml, will back up all the information in the previously described volumes.

If no volumes exists, and there is already a backup, then the ansible playbooks will create new volumes and reload data from Backups.

It is recommended you leverage the task-backup-vol-container.yml and build a regular backup scheme.