Better README display?
This commit is contained in:
parent
17fef409a8
commit
5ee1c774ac
1 changed files with 7 additions and 3 deletions
|
@ -179,6 +179,7 @@ Configuration
|
|||
Set ``SOCIALACCOUNT_ADAPTER='allauth_ens.adapter.LongTermClipperAccountAdapter'``
|
||||
in `settings.py`
|
||||
|
||||
|
||||
Auto-signup
|
||||
Populated data
|
||||
- username: ``<clipper>@<entrance year>``
|
||||
|
@ -188,6 +189,7 @@ Auto-signup
|
|||
and *promotion* parsed from LDAP's *homeDirectory* field (available only on
|
||||
first connection)
|
||||
|
||||
|
||||
Account deprecation
|
||||
At the beginning of each year (i.e. early November), to prevent clipper
|
||||
username conflicts, you should run ``$ python manage.py deprecate_clippers``.
|
||||
|
@ -196,6 +198,7 @@ Account deprecation
|
|||
(using LDAP), so that a known user keeps his account, but a newcomer won't
|
||||
inherit an archicube's.
|
||||
|
||||
|
||||
Customize
|
||||
You can customize the SocialAccountAdapter by inheriting
|
||||
``allauth_ens.adapter.LongTermClipperAccountAdapter``. You might want to
|
||||
|
@ -206,6 +209,7 @@ Customize
|
|||
``get_username`` (as done in the example website) allows to get rid of that
|
||||
behaviour, and for instance attribute a default entrance year.
|
||||
|
||||
|
||||
Initial migration
|
||||
If you used allauth without LongTermClipperAccountAdapter, or another CAS
|
||||
interface to log in, you need to update the Users to the new username policy,
|
||||
|
|
Loading…
Reference in a new issue