Open dragonchaser opened 7 months ago
/cc @micbar && @mmattel
The reason for different prefixes is to allow changing the configuration of individual services when running in a single process.
We shoud phase out as many service specific variables as soon as possible. But they will need to stay in for backwards compatability.
I'm looking at the ServiceAccountsID env var which is another special case as every service should use a dedicated service account id. but then the settings service needs to know all accounts...
The reason for different prefixes is to allow changing the configuration of individual services when running in a single process.
We shoud phase out as many service specific variables as soon as possible. But they will need to stay in for backwards compatability.
Already possible, using our deprecation system, it would be awesome if we could get rid of that with 6.0. It would be desirable to have only one variable per annotation and move global vars to
ocis-pkg
I'm looking at the ServiceAccountsID env var which is another special case as every service should use a dedicated service account id. but then the settings service needs to know all accounts...
:+1:
And we need to clarify how config parsing works in the docs https://owncloud.dev/ocis/config/
UP
At the moment we have tons of redundant environment variables that do not make sense IMHO. For example we configure
OCIS_LOG_LEVEL
,OCIS_LOG_PRETTY
,OCIS_LOG_COLOR
,OCIS_LOG_FILE
for every service. It would be sufficient to define three of them (OCIS_LOG_PRETTY
,OCIS_LOG_COLOR
andOCIS_LOG_FILE
) globally and just define a log level per service. This also applies to other variables and variable groups (e.g. Debug, RevaGateway etc.).