-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Add parameter "enable_id_obfuscation" to environment variables #29
Comments
But its hardcode to 'true'. I want to set 'false' via docker evironemnt variables. |
We honestly didn't think anyone would want it off. You can customize the container via https://www.linuxserver.io/blog/2019-09-14-customizing-our-containers |
For example I use this image in AWS Elastic Container Service, and to change this parameter I need to add custom scripts that will be mounted to container to change only 1 parameter on every start of container instance... I can rebuild container and stored it in my private repo (only because of 1 parameter) OR I need to generate whole results/telemetry_settings.php thta will be mounted to results/telemetry_settings.php mount file, and your script that set Vars inside it, is not needed anymore. |
We do not plan to add additional envvars, but you can customize as you see fit per aptalca's comment. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is this a new feature request?
Wanted change
Want to set parameter "enable_id_obfuscation" from results/telemetry_settings.php via docker environment variables
Reason for change
If I want to change this parameter in results/telemetry_settings.php I had to re-write file telemetry_settings.php. It will be easier if this parameter can be set as all other parameters (DB_,IPINFO_APIKEY, etc) via env variables.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: