zulip

mirror of https://github.com/zulip/zulip.git synced 2025-11-15 11:22:04 +00:00

Files

Greg Price a612049ac4 docs: Expand on LDAP config; try to clarify "username" concept.

The term "username" confusingly refers both to the Django concept of
"username" (meaning "the name the user types into the login form") and
a concept the admin presumably already has in their existing
environment; which may or may not be the same thing, and in fact this
is where we document the admin's choice of whether and how they should
correspond.  The Django concept in particular isn't obvious, and is
counterintuitive when it means something like an email address.

Explicitly explain the Django "username" concept, under the name of
"Zulip username" to take responsibility for our choice of how it's
exposed in the settings interface.  Then use an explicit qualifier,
like "LDAP username", whenever referring to some other notion of
username.  And make a pass over this whole side of the instructions,
in particular for consistent handling of these concepts.

2018-09-27 13:20:10 -07:00

authentication-methods.md

docs: Expand on LDAP config; try to clarify "username" concept.

2018-09-27 13:20:10 -07:00

deployment.md

docs: Expand documentation of running Zulip behind a reverse proxy.

2018-08-02 08:38:56 -07:00

email.md

docs: Remove use of multi-line 'su zulip' in docs.

2018-07-30 13:38:55 -07:00

expensive-migrations.md

models: Add new UserMessage flag active_mobile_push_notification.