Inventory and clarify how each auto-config value is handled [WIP] #2224
Labels
2. developing
docs
enhancement
feature: auto config (Docker secrets)
feature: auto config (environment variables)
Auto configuring via environment variables
technical debt
Milestone
We currently inject auto config variable a variety of ways.
Some:
config.php
if they're provided at install timeconfig.php
These creates confusion in a variety of ways:
config.php
"?config.php
"?config.php
and other times they don't?"config.php
values completely out-of-sync?"Here I'll attempt to inventory and analyze each variable so that we can then:
TODO:
autoconfig.php
will be accessed aswww-data
notroot
/root equivalent)Background:
NC_*
environment variables with Nextcloud Server via the image #2226), but not documented upstream (but something we tend to suggest when people request new variables to adjust Server parameters get added here) nor documented for the image formally either officiallyWe likely can't fix all of them, but we can document them clearly. And, in the process, possibly also make some implementation adjustments where it make sense.
The variations (this basically needs to be translated into a big table or something):
entrypoint.sh
autoconfig.php
config.php
config.php
occ config:list system
config/*.config.php
)Installation time only:
entrypoint.sh
(or) via Server'sautoconfig.php
autoconfig.php
support if used without NEXTCLOUD_ADMIN_* (pulled in by Server's installer)entrypoint.sh
(or) via Server'sautoconfig.php
autoconfig.php
support if used without NEXTCLOUD_ADMIN_* (pulled in by Server's installer)entrypoint.sh
(or) via Server'sautoconfig.php
autoconfig.php
support if used without NEXTCLOUD_ADMIN_* (pulled in by Server's installer)entrypoint.sh
(or) via Server'sautoconfig.php
autoconfig.php
support if used without NEXTCLOUD_ADMIN_* (pulled in by Server's installer)Anytime
config/config.php
config/reverse.proxy.php
The text was updated successfully, but these errors were encountered: