4 ms·

We support this, it's just enough of a corner case that it's not well documented. If you don't care about missed-message emails, you can install the Docker ima

We support this, it's just enough of a corner case that it's not well documented. If you don't care about missed-message emails, you can install the Docker image (easiest to setup when offline), and then use https://zulip.readthedocs.io/en/latest/production/authentication-methods.html#apache-based-sso-with-remote-user https://zulip.readthedocs.io/en/latest/production/authentica... with an Apache .htaccess file as the thing that sets REMOTE_USER. Send a message in "#production help" in chat.zulip.org if you have trouble figuring it out, and I'll extend the docs until you can get it working.

hiisukun 8y ago
Well, that's a great reply. Having read quickly through the docs, I think in particular the "Life of an Apache-based SSO login attempt" had enough information to clarify the process for me - until then I wasn't as sure. I don't think I would have located this option while filtering for "works without email, and I'm okay missing messages". If it was present a year ago I definitely didn't. Very glad it's a supported corner case!
- tabbott 8y ago
  Yeah, the front-page documentation focuses pretty heavily on "you should setup email" because it helps folks in a normal environment successfully setup Zulip quickly and reliably. I'm not sure whether this use case is common enough that we should put it in the front-page docs, but possibly we should write something that Google will find...
  - bj0 8y ago
    I looked at Zulip vs Mattermost several months ago and, if I recall correctly, this was one of the primary reasons I went with Mattermost. I just wanted something I could spin up in docker on a vps without having to setup anything else (like an email server). Mattermost lets you generate "invite links" that you can just paste in a chat or text message. The other really neat feature was having multiple "teams" on a single server.
    - seedie 8y ago
      Hi, I don't know enough about Mattermost to be sure I understand you correctly about 'multiple "teams" on a single server' but you can host multiple organizations (realms in zulip-speak) on a single zulip server https://zulip.readthedocs.io/en/latest/production/multiple-organizations.html https://zulip.readthedocs.io/en/latest/production/multiple-o... edit: link updated to point to official documentation instead of github
      - bj0 8y ago
        That's neat, I may look at zulip again if I need to setup another server. From a quick glance, the differences I see are: * In mattermost, different "teams" (or "realms" or "namespaces", whatever) exist on the same server (same url), and a user account that logs in will only see the teams they are assigned to. A single user account can be assigned to multiple teams (they appear on the left, similar to how the slack desktop app shows multiple server connections). * Zulip requires a different subdomain for each "realm", and it sounds like users have to log into each one separately. It is not clear if the same account is shared between organizations or a user must have separate accounts. So it sounds like Zulip's approach is separate, isolated "organizations", like slack, just hosted on the same server. Where Mattermost's approach is more like having separate, but integrated teams/groups/namespaces that a single account can be part of.
        vishnu_ks 8y ago
        > So it sounds like Zulip's approach is separate, isolated "organizations", like slack, just hosted on the same server. Correct. But Zulip does allow to import settings, profile picture etc from an existing account during signup if the email remains the same.

hiisukun 8y ago

Well, that's a great reply. Having read quickly through the docs, I think in particular the "Life of an Apache-based SSO login attempt" had enough information to clarify the process for me - until then I wasn't as sure. I don't think I would have located this option while filtering for "works without email, and I'm okay missing messages". If it was present a year ago I definitely didn't. Very glad it's a supported corner case!

tabbott 8y ago
Yeah, the front-page documentation focuses pretty heavily on "you should setup email" because it helps folks in a normal environment successfully setup Zulip quickly and reliably. I'm not sure whether this use case is common enough that we should put it in the front-page docs, but possibly we should write something that Google will find...
- bj0 8y ago
  I looked at Zulip vs Mattermost several months ago and, if I recall correctly, this was one of the primary reasons I went with Mattermost. I just wanted something I could spin up in docker on a vps without having to setup anything else (like an email server). Mattermost lets you generate "invite links" that you can just paste in a chat or text message. The other really neat feature was having multiple "teams" on a single server.
  - seedie 8y ago
    Hi, I don't know enough about Mattermost to be sure I understand you correctly about 'multiple "teams" on a single server' but you can host multiple organizations (realms in zulip-speak) on a single zulip server https://zulip.readthedocs.io/en/latest/production/multiple-organizations.html https://zulip.readthedocs.io/en/latest/production/multiple-o... edit: link updated to point to official documentation instead of github
    - bj0 8y ago
      That's neat, I may look at zulip again if I need to setup another server. From a quick glance, the differences I see are: * In mattermost, different "teams" (or "realms" or "namespaces", whatever) exist on the same server (same url), and a user account that logs in will only see the teams they are assigned to. A single user account can be assigned to multiple teams (they appear on the left, similar to how the slack desktop app shows multiple server connections). * Zulip requires a different subdomain for each "realm", and it sounds like users have to log into each one separately. It is not clear if the same account is shared between organizations or a user must have separate accounts. So it sounds like Zulip's approach is separate, isolated "organizations", like slack, just hosted on the same server. Where Mattermost's approach is more like having separate, but integrated teams/groups/namespaces that a single account can be part of.
      - vishnu_ks 8y ago
        > So it sounds like Zulip's approach is separate, isolated "organizations", like slack, just hosted on the same server. Correct. But Zulip does allow to import settings, profile picture etc from an existing account during signup if the email remains the same.