The default theme of Django Contrib Admin is not really great. This
theme the Django Admin with Re2o logo and colors.
It also comes with a new dynamic-generated menu to navigate in the admin
interface.
A new index page override the global index of Django Contrib Admin to
prepare for new features.
This patch is part of the Aube patchset for Re2o, targeting the use of
Django Contrib Admin as a manage interface for active members.
This patch remove the custom rule in router responsible to redirect
logout to index page and place a template with pre-translated strings.
This is part of Aube patchset for Re2o to unify the login procedure with
Django Contrib Auth.
Without this patch, Re2o has two login screen with different
features.
This patch redirects `/admin/login/` to the login page.
This patch is part of the Aube patchset for Re2o. This helps in the goal
to unify the login process and drop the custom login page.
Now compiled locale files (.mo) are generated on the server side.
This cleans up the git tree and make translation contributions much
easier to merge.
Please note that you will need to generate those files after each pull,
so remember to execute install_re2o.sh.
Now `manage.py gen_contrib` generates a contributors.py matching the
already existing format. It normalizes names to make the list more
enjoyable.
Before using this to seriously generate contributors.py we need to
figure out a way to add pseudo names, or tell everyone to change their
name on GitLab.
* Rather than using href="\\host/about/" in page footer, use
href="protocol://host/about/"
* The old footer uses hacks to be staticly on the bottom. To make it
much simpler one solution is to turn it white and use official
Bootstrap code. This leads to less CSS to maintain and better
cross-browser compatibility.
* On re2o about page (/about/) there is some typos such as :
* assocations > associations
* legitlab > le gitlab
* Use Bootstrap navbar-static-top rather than custom CSS.
The result is the same, so we should be better using directly
Bootstrap CSS.
An attacker knowing the salt but not the hash could try timming-attacks
to guess a password hash and then try to find it from the hash.
Although not a high risk, there is no good reason not to use a
constant-time comparison, hence this commit.
