Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Handle the case where BCFG2_CONFIG_FILE isn't set in the environment | Michael Fenn | 2014-04-11 | 1 | -2/+2 |
| | |||||
* | Parse the config inside of the wsgi application function | Michael Fenn | 2014-04-09 | 1 | -2/+11 |
| | | | | | | If you don't set this, the parsing code will always look in /etc/bcfg2.conf for the config, which might not exist or be readable by apache in a standard config. | ||||
* | reports.wsgi: Fix indentation | Sol Jerome | 2014-03-20 | 1 | -1/+1 |
| | | | | Signed-off-by: Sol Jerome <sol.jerome@gmail.com> | ||||
* | reports: set DJANGO_SETTINGS_MODULE in wsgi script | Chris St. Pierre | 2014-03-05 | 1 | -0/+2 |
| | |||||
* | DB: fixed how Django settings are loaded | Chris St. Pierre | 2013-10-30 | 1 | -4/+5 |
| | |||||
* | Web Reports: allow bcfg2.conf to be passed to the wsgi app | Tim Laszlo | 2012-09-21 | 1 | -1/+6 |
| | | | | | | | This allows users to specify alternate config files in the apache config SetEnv BCFG2_CONFIG_FILE /path/to/bcfg2.conf WSGIScriptAlias /bcfg2 /path/to/reports.wsgi | ||||
* | Merge reporting configuration with main server configuration | Tim Laszlo | 2012-08-07 | 1 | -1/+1 |
| | | | | | | Admin/Syncdb: Use SchemaUpdater Move the schema update routines from reports to Bcfg2.Server Move Reports.settings into Bcfg2.settings | ||||
* | web_reports: Moved location of reports.wsgi to a more stable location | Tim Laszlo | 2010-10-21 | 1 | -0/+4 |