Apologies if I needed to submit this as an idea first, but I thought others could potentially find this useful. If the environment variable is not provided, then the application will default to expecting the config file at the ROOTPATH.
More detail:
I created this feature in a fork so that I can mount a config file stored in Azure File Storage as a volume in my container in an Azure App Service. Azure currently requires users to mount the entire storage container as a volume (instead of just mounting an individual file), therefore I wasn't able to mount it to /var/wiki since it would hide all the existing files.
Apologies if I needed to submit this as an idea first, but I thought others could potentially find this useful. If the environment variable is not provided, then the application will default to expecting the config file at the ROOTPATH.
More detail:
I created this feature in a fork so that I can mount a config file stored in Azure File Storage as a volume in my container in an Azure App Service. Azure currently requires users to mount the entire storage container as a volume (instead of just mounting an individual file), therefore I wasn't able to mount it to /var/wiki since it would hide all the existing files.
My docker-compose file can now look like:
version: "3" services: wikijs: image:
ports: