You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting logging configuration file name from an environment variable would allow using a custom configuration on local development. Like that, editing the checked-in logconfig.ini would be no longer necessary and these modified files would get accidentally committed. That already happened a few times.
This environment variable would be loaded by the run_gunicorn.py script. It’d default to the current logconfig.ini.
It’s possible to use the INVENTORY_LOGGING_CONFIG_FILE variable name already mentioned in the README.
The text was updated successfully, but these errors were encountered:
Getting logging configuration file name from an environment variable would allow using a custom configuration on local development. Like that, editing the checked-in logconfig.ini would be no longer necessary and these modified files would get accidentally committed. That already happened a few times.
This environment variable would be loaded by the run_gunicorn.py script. It’d default to the current logconfig.ini.
It’s possible to use the INVENTORY_LOGGING_CONFIG_FILE variable name already mentioned in the README.
The text was updated successfully, but these errors were encountered: