-
Jan Mach authored
The auth_dev authentication module was accidentaly enabled by default in configuration file shipped with Mentat packages. It was changed at some point locally during development and the change was accidentally committed. The documentation was missing the warning about disabling it during installation in production deployment. This is fixed now.
Jan Mach authoredThe auth_dev authentication module was accidentaly enabled by default in configuration file shipped with Mentat packages. It was changed at some point locally during development and the change was accidentally committed. The documentation was missing the warning about disabling it during installation in production deployment. This is fixed now.
hawat.local.conf 1.06 KiB
SECRET_KEY = 'local-secret-key'
MAIL_SERVER = 'localhost'
MAIL_PORT = 8025
MAIL_DEFAULT_SENDER = 'mentat@cesnet.cz'
HAWAT_LOG_DEFAULT_LEVEL = 'debug'
HAWAT_LOG_FILE = '/var/tmp/mentat-hawat.py.log'
HAWAT_LOG_FILE_LEVEL = 'debug'
ENABLED_BLUEPRINTS = [
'vial.blueprints.auth',
'vial.blueprints.auth_api',
'vial.blueprints.design_bs3',
'vial.blueprints.devtools',
'vial.blueprints.changelogs',
'hawat.blueprints.auth_env',
'hawat.blueprints.auth_dev',
'hawat.blueprints.auth_pwd',
'hawat.blueprints.home',
'hawat.blueprints.reports',
'hawat.blueprints.events',
'hawat.blueprints.hosts',
'hawat.blueprints.timeline',
'hawat.blueprints.dnsr',
#'hawat.blueprints.pdnsr',
'hawat.blueprints.geoip',
#'hawat.blueprints.nerd',
'hawat.blueprints.whois',
'hawat.blueprints.performance',
'hawat.blueprints.status',
'hawat.blueprints.dbstatus',
'hawat.blueprints.users',
'hawat.blueprints.groups',
'hawat.blueprints.settings_reporting',
'hawat.blueprints.filters',
'hawat.blueprints.networks',
]