mirror of
https://github.com/wger-project/wger.git
synced 2026-02-18 00:17:51 +01:00
1fa288876c
For certain deployments, users should not be able to register on their own, but should be added by the appropriate gym managers. This can now be configured in the global settings file Fixes #220
28 lines
1004 B
ReStructuredText
28 lines
1004 B
ReStructuredText
.. _settings:
|
|
|
|
Settings
|
|
========
|
|
|
|
You can configure some of the application behaviour with the ``WGER_SETTINGS``
|
|
dictionary in your settings file. Currently the following options are supported:
|
|
|
|
**ALLOW_REGISTRATION**: Default ``True``.
|
|
Controls whether users can register on their own or if a gym adminstrator has
|
|
to create the user accounts.
|
|
|
|
**USE_RECAPTCHA**: Default ``False``.
|
|
Controls whether a captcha challenge will be presented when new users register.
|
|
|
|
**REMOVE_WHITESPACE**: Default ``False``.
|
|
Removes whitespaces around HTML tags to reduce the size of the resulting HTML.
|
|
If you are not serving the site using TLS you probably want to use the GZip
|
|
middleware instead. Read the django documentation on the security implications
|
|
(BREACH attack).
|
|
|
|
|
|
.. note::
|
|
If you want to override a default setting, don't overwrite all the dictionary
|
|
but only the keys you need, e.g. ``WGER_SETTINGS['foo'] = 'bar'``. This avoids
|
|
problems when new keys are added in the global settings.
|
|
|