Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
converse.js
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
converse.js
Commits
c9106209
Commit
c9106209
authored
Oct 24, 2012
by
Michal Čihař
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document ways of locking down Weblate (issue #131)
parent
ab6b5d9c
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
53 additions
and
0 deletions
+53
-0
docs/admin.rst
docs/admin.rst
+4
-0
docs/config.rst
docs/config.rst
+35
-0
weblate/settings_example.py
weblate/settings_example.py
+14
-0
No files found.
docs/admin.rst
View file @
c9106209
...
...
@@ -263,6 +263,10 @@ group, which will be allowed to save translations and manage suggestions) and
add selected users to this group. You can do all this from Django admin
interface.
To completely lock down your Weblate installation you can use
:setting:`LOGIN_REQUIRED_URLS` for forcing users to login and
:setting:`REGISTRATION_OPEN` for disallowing new registrations.
.. _lazy-commit:
Lazy commits
...
...
docs/config.rst
View file @
c9106209
...
...
@@ -51,6 +51,41 @@ translator.
.. seealso:: :ref:`locking`
.. setting:: LOGIN_REQUIRED_URLS
LOGIN_REQUIRED_URLS
-------------------
List of URL which require login (besides standard rules built into Weblate).
This allows you to password protect whole installation using:
.. code-block:: python
LOGIN_REQUIRED_URLS = (
r'/(.*)$',
)
.. setting:: LOGIN_REQUIRED_URLS_EXCEPTIONS
LOGIN_REQUIRED_URLS_EXCEPTIONS
------------------------------
List of exceptions for :setting:`LOGIN_REQUIRED_URLS`, in case you won't
specify this list, the default value will be used, which allows users to access
login page.
Some of exceptions you might want to include:
.. code-block:: python
LOGIN_REQUIRED_URLS_EXCEPTIONS = (
r'/accounts/(.*)$', # Required for login
r'/media/(.*)$', # Required for development mode
r'/widgets/(.*)$', # Allowing public access to widgets
r'/data/(.*)$', # Allowing public access to data exports
r'/hooks/(.*)$', # Allowing public access to notification hooks
)
.. setting:: CHECK_LIST
CHECK_LIST
...
...
weblate/settings_example.py
View file @
c9106209
...
...
@@ -344,3 +344,17 @@ DEFAULT_FROM_EMAIL = 'webmaster@localhost'
# 'LOCATION': '127.0.0.1:11211',
# }
#}
# Example for restricting access to logged in users
#LOGIN_REQUIRED_URLS = (
# r'/(.*)$',
#)
# In such case you will want to include some of the exceptions
#LOGIN_REQUIRED_URLS_EXCEPTIONS = (
# r'/accounts/(.*)$', # Required for login
# r'/media/(.*)$', # Required for development mode
# r'/widgets/(.*)$', # Allowing public access to widgets
# r'/data/(.*)$', # Allowing public access to data exports
# r'/hooks/(.*)$', # Allowing public access to notification hooks
#)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment