Which files need to be persisted to keep WebUI configuration changes through container restarts?

[aq-daniel]

Thank you for your work and providing a containerized version of RaspAP. 👍 It's a good solution to use containerized RaspAP, if you have other services running beside it on your host device.

Now to my current problem:
I can successfully set some settings through the environment variables in the docker-compose.yml like RASPAP_SSID, WEBGUI_PORT, etc.
That's good and is working, but if I change any settings (e.g. Wireless Mode) or add for example an opnvpn config-file through the webui, it doesn't persist container restarts.

The correct solution for this problem seems to be a docker volume as mentioned in another discussion here.
So my questions are:

1. Which files need to be mounted to a docker volume to persist setting changes through the WebUI over container restarts? Is there a list of all config files somewhere?
2. Does a config folder exist in the container, which could be bound to a volume? In the docs is a config directory mentioned, but I couldn't find it inside the docker container.
3. I tried binding /var/www/html/includes to a docker volume as this directory contains the config.php, but it doesn't seem to work for persisting the wirelss mode setting over restarts. Which file contains the setting for the wireless mode?

[billz]

Hi, great questions. All of the file paths used by the application are defined in config.php. Persisting these to a docker volume will get you most of the way there. Note that the individual files defined here, not just config.php itself, must be saved to a storage volume if your goal is to persist all application settings through container restarts. RaspAP stores user preferences in /etc/raspap, so you could persist the contents of this directory as well.

Hope this gets you started in the right directions, and please do share your results! We can look at adding steps in the official docs to assist other users.