summaryrefslogtreecommitdiffstats
path: root/reports/reports.wsgi
Commit message (Collapse)AuthorAgeFilesLines
* Reports: Use try/except and no version comparisonAlexander Sulfrian2015-09-291-3/+2
|
* some more django 1.7 compatibility fixesJonas Jochmaring2015-09-231-12/+13
|
* make Bcfg2-web compatible with django 1.7Jonas Jochmaring2015-09-231-13/+15
| | | | | | - reports.wsgi uses get_wsgi_application() now - old south-based migrations have been moved - manage.py has been updated
* Handle the case where BCFG2_CONFIG_FILE isn't set in the environmentMichael Fenn2014-04-111-2/+2
|
* Parse the config inside of the wsgi application functionMichael Fenn2014-04-091-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 indentationSol Jerome2014-03-201-1/+1
| | | | Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
* reports: set DJANGO_SETTINGS_MODULE in wsgi scriptChris St. Pierre2014-03-051-0/+2
|
* DB: fixed how Django settings are loadedChris St. Pierre2013-10-301-4/+5
|
* Web Reports: allow bcfg2.conf to be passed to the wsgi appTim Laszlo2012-09-211-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 configurationTim Laszlo2012-08-071-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 locationTim Laszlo2010-10-211-0/+4