mirror of https://github.com/zulip/zulip.git
119bc14182
The main limitation of this version is that it's controlled entirely from settings, with nothing in the database and no web UI or even management command to control it. That makes it a bit more of a burden for the server admins than it'd ideally be, but that's fine for now. Relatedly, the web flow for realm creation still requires choosing a subdomain even if the realm is destined to live at an alias domain. Specific to the dev environment, there is an annoying quirk: the special dev login flow doesn't work on a REALM_HOSTS realm. Also, in this version the `add_new_realm` and `add_new_user` management commands, which are intended for use in development environments only, don't support this feature. In manual testing, I've confirmed that a REALM_HOSTS realm works for signup and login, with email/password, Google SSO, or GitHub SSO. Most of that was in dev; I used zulipstaging.com to also test * logging in with email and password; * logging in with Google SSO... far enough to correctly determine that my email address is associated with some other realm. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| lib | ||
| management | ||
| migrations | ||
| templatetags | ||
| tests | ||
| tornado | ||
| views | ||
| webhooks | ||
| worker | ||
| __init__.py | ||
| apps.py | ||
| context_processors.py | ||
| decorator.py | ||
| filters.py | ||
| forms.py | ||
| logging_handlers.py | ||
| middleware.py | ||
| models.py | ||
| signals.py | ||
| static_header.txt | ||
| storage.py | ||