2013-11-14 05:14:18 +01:00
|
|
|
# Settings for Zulip Enterprise
|
|
|
|
|
|
|
|
### MANDATORY SETTINGS
|
2013-10-23 23:28:03 +02:00
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# The user-accessible Zulip hostname for this installation, e.g.
|
|
|
|
# zulip.example.com
|
2013-10-25 21:19:30 +02:00
|
|
|
EXTERNAL_HOST = ''
|
2013-10-17 16:33:04 +02:00
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# The email address for the person or team who maintain the Zulip
|
2013-11-16 00:47:17 +01:00
|
|
|
# Enterprise installation. Will also get support emails. (e.g. zulip-admin@example.com)
|
2013-11-04 19:37:05 +01:00
|
|
|
ZULIP_ADMINISTRATOR = ''
|
2013-11-13 15:59:59 +01:00
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# The domain for your organization, e.g. example.com
|
2013-11-10 16:12:02 +01:00
|
|
|
ADMIN_DOMAIN = ''
|
2013-11-04 19:37:05 +01:00
|
|
|
|
2013-11-14 18:38:09 +01:00
|
|
|
# The deployment key is used by your server to authenticate any
|
|
|
|
# communication with Zulip. You can obtain your key from
|
|
|
|
# https://zulip.com/enterprise/download/deployment-key
|
2013-10-17 16:33:04 +02:00
|
|
|
DEPLOYMENT_ROLE_KEY = ''
|
2013-10-23 23:28:03 +02:00
|
|
|
|
2013-11-13 15:59:59 +01:00
|
|
|
# Enable at least one of the following authentication backends.
|
|
|
|
AUTHENTICATION_BACKENDS = (
|
|
|
|
# 'zproject.backends.EmailAuthBackend', # Email and password
|
2013-11-13 16:45:16 +01:00
|
|
|
# 'zproject.backends.ZulipRemoteUserBackend', # Local SSO
|
2013-11-13 15:59:59 +01:00
|
|
|
# 'zproject.backends.GoogleBackend', # Google Apps
|
|
|
|
)
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# If you are using the ZulipRemoteUserBackend authentication backend,
|
|
|
|
# set this to your domain (e.g. if REMOTE_USER is "username" and the
|
|
|
|
# corresponding email address is "username@example.com", set
|
|
|
|
# SSO_APPEND_DOMAIN = "example.com")
|
2013-11-13 15:59:59 +01:00
|
|
|
SSO_APPEND_DOMAIN = None
|
|
|
|
|
2013-10-25 21:19:30 +02:00
|
|
|
# Configure the outgoing SMTP server below. For outgoing email
|
|
|
|
# via a GMail SMTP server, EMAIL_USE_TLS must be True and the
|
|
|
|
# outgoing port must be 587. The EMAIL_HOST is prepopulated
|
2013-11-05 01:19:52 +01:00
|
|
|
# for GMail servers, change it for other hosts, or leave it unset
|
|
|
|
# or empty to skip sending email.
|
2013-10-25 21:19:30 +02:00
|
|
|
EMAIL_HOST = 'smtp.gmail.com'
|
2013-10-23 23:28:03 +02:00
|
|
|
EMAIL_HOST_USER = ''
|
|
|
|
EMAIL_HOST_PASSWORD = ''
|
|
|
|
EMAIL_PORT = 587
|
2013-11-05 01:19:52 +01:00
|
|
|
EMAIL_USE_TLS = True
|
2013-10-23 23:28:03 +02:00
|
|
|
|
2013-11-16 00:47:17 +01:00
|
|
|
# The email From address to be used for automatically generated emails
|
|
|
|
DEFAULT_FROM_EMAIL = "Zulip <zulip@example.com>"
|
|
|
|
# The noreply address to be used as Reply-To for certain generated emails.
|
|
|
|
# Messages sent to this address should not be delivered anywhere.
|
|
|
|
NOREPLY_EMAIL_ADDRESS = "noreply@example.com"
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
### OPTIONAL SETTINGS
|
2013-11-14 05:14:18 +01:00
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# Controls whether session cookies expire when the browser closes
|
2013-11-14 05:14:18 +01:00
|
|
|
SESSION_EXPIRE_AT_BROWSER_CLOSE = False
|
|
|
|
|
|
|
|
# Session cookie expiry in seconds after the last page load
|
2013-11-14 05:25:45 +01:00
|
|
|
SESSION_COOKIE_AGE = 60 * 60 * 24 * 7 * 2 # 2 weeks
|
2013-11-14 05:14:18 +01:00
|
|
|
|
2013-11-25 22:07:37 +01:00
|
|
|
# Controls whether or not there is a feedback button in the UI.
|
2013-11-13 16:59:03 +01:00
|
|
|
ENABLE_FEEDBACK = True
|
|
|
|
|
2013-11-25 22:07:37 +01:00
|
|
|
# By default, the feedback button will submit feedback to the Zulip
|
|
|
|
# developers. If you set FEEDBACK_EMAIL to be an email address
|
|
|
|
# (e.g. ZULIP_ADMINISTRATOR), feedback sent by your users will instead
|
|
|
|
# be sent to that email address.
|
|
|
|
# FEEDBACK_EMAIL = ZULIP_ADMINISTRATOR
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# Controls whether or not error reports are sent to Zulip. Error
|
|
|
|
# reports are used to improve the quality of the product and do not
|
|
|
|
# include message contents; please contact Zulip support with any
|
|
|
|
# questions.
|
2013-11-13 21:35:04 +01:00
|
|
|
ERROR_REPORTING = True
|
|
|
|
|
2013-11-14 14:37:39 +01:00
|
|
|
# Controls whether or not Zulip will provide inline image preview when
|
|
|
|
# a link to an image is referenced in a message.
|
|
|
|
INLINE_IMAGE_PREVIEW = True
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# By default, files uploaded by users and user avatars are stored
|
|
|
|
# directly on the Zulip server. If file storage in Amazon S3 (or
|
|
|
|
# elsewhere, e.g. your corporate fileshare) is desired, please contact
|
|
|
|
# Zulip Support (support@zulip.com) for further instructions on
|
|
|
|
# setting up the appropriate integration.
|
2013-10-28 16:13:53 +01:00
|
|
|
LOCAL_UPLOADS_DIR = "/home/zulip/uploads"
|
2013-10-23 23:28:03 +02:00
|
|
|
|
2013-11-15 16:52:31 +01:00
|
|
|
# Controls whether name changes are completely disabled for this installation
|
|
|
|
# This is useful in settings where you're syncing names from an integrated LDAP/Active Directory
|
|
|
|
NAME_CHANGES_DISABLED = False
|
|
|
|
|
2013-11-15 22:25:02 +01:00
|
|
|
# Controls whether users who have not uploaded an avatar will receive an avatar
|
|
|
|
# from gravatar.com.
|
|
|
|
ENABLE_GRAVATAR = True
|
|
|
|
|
2013-11-18 16:58:39 +01:00
|
|
|
# To override the default avatar image if ENABLE_GRAVATAR is False, place your
|
|
|
|
# custom default avatar image at /home/zulip/local-static/default-avatar.png
|
|
|
|
# and uncomment the following line.
|
|
|
|
#DEFAULT_AVATAR_URI = '/local-static/default-avatar.png'
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
### TWITTER INTEGRATION
|
|
|
|
|
|
|
|
# Zulip supports showing inline Tweet previews when a tweet is linked
|
|
|
|
# to in a message. To support this, Zulip must have access to the
|
|
|
|
# Twitter API via OAuth. To obtain the various access tokens needed
|
|
|
|
# below, you must register a new application under your Twitter
|
|
|
|
# account by doing the following:
|
2013-10-25 21:19:30 +02:00
|
|
|
#
|
|
|
|
# 1. Log in to http://dev.twitter.com.
|
|
|
|
# 2. In the menu under your username, click My Applications. From this page, create a new application.
|
|
|
|
# 3. Click on the application you created and click "create my access token". Fill in the requested values.
|
|
|
|
TWITTER_CONSUMER_KEY = ''
|
|
|
|
TWITTER_CONSUMER_SECRET = ''
|
|
|
|
TWITTER_ACCESS_TOKEN_KEY = ''
|
|
|
|
TWITTER_ACCESS_TOKEN_SECRET = ''
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
### EMAIL GATEWAY INTEGRATION
|
|
|
|
|
|
|
|
# The email gateway provides, for each stream, an email address that
|
|
|
|
# you can send email to in order to have the email's content be posted
|
|
|
|
# to that stream. Emails received at the per-stream email address
|
|
|
|
# will be converted into a Zulip message
|
2013-11-12 16:19:38 +01:00
|
|
|
|
|
|
|
# The email address pattern to use for auto-generated stream emails
|
|
|
|
# The %s will be replaced with a unique token, and the resulting email
|
2013-11-14 05:25:45 +01:00
|
|
|
# must be delivered to the EMAIL_GATEWAY_IMAP_FOLDER of the
|
|
|
|
# EMAIL_GATEWAY_LOGIN account below.
|
|
|
|
#
|
|
|
|
# Example: zulip+%s@example.com
|
2013-11-12 16:19:38 +01:00
|
|
|
EMAIL_GATEWAY_PATTERN = ""
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# The Zulip username of the bot that the email pattern should post as.
|
|
|
|
# Example: emailgateway@example.com
|
2013-11-12 16:19:38 +01:00
|
|
|
EMAIL_GATEWAY_BOT = ""
|
|
|
|
|
|
|
|
# Configuration of the email mirror mailbox
|
|
|
|
# The IMAP login and password
|
|
|
|
EMAIL_GATEWAY_LOGIN = ""
|
|
|
|
EMAIL_GATEWAY_PASSWORD = ""
|
|
|
|
# The IMAP server & port to connect to
|
|
|
|
EMAIL_GATEWAY_IMAP_SERVER = ""
|
|
|
|
EMAIL_GATEWAY_IMAP_PORT = 993
|
|
|
|
# The IMAP folder name to check for emails. All emails sent to EMAIL_GATEWAY_PATTERN above
|
|
|
|
# must be delivered to this folder
|
|
|
|
EMAIL_GATEWAY_IMAP_FOLDER = "INBOX"
|
|
|
|
|
2013-11-21 01:30:20 +01:00
|
|
|
### LDAP integration configuration
|
|
|
|
# Zulip supports retrieving information about users via LDAP, and optionally
|
|
|
|
# using LDAP as an authentication mechanism.
|
|
|
|
|
|
|
|
import ldap
|
|
|
|
from django_auth_ldap.config import LDAPSearch, GroupOfNamesType
|
|
|
|
|
|
|
|
# URI of your LDAP server. If set, LDAP is used to prepopulate a user's name in
|
|
|
|
# Zulip. Example: "ldaps://ldap.example.com"
|
|
|
|
AUTH_LDAP_SERVER_URI = ""
|
|
|
|
|
|
|
|
# This DN and password will be used to bind to your server. If unset, anonymous
|
|
|
|
# binds are performed.
|
|
|
|
AUTH_LDAP_BIND_DN = ""
|
|
|
|
AUTH_LDAP_BIND_PASSWORD = ""
|
|
|
|
|
2013-11-22 22:58:22 +01:00
|
|
|
# Specify the search base and the property to filter on that corresponds to the
|
2013-11-21 01:30:20 +01:00
|
|
|
# username.
|
|
|
|
AUTH_LDAP_USER_SEARCH = LDAPSearch("ou=users,dc=example,dc=com",
|
|
|
|
ldap.SCOPE_SUBTREE, "(uid=%(user)s)")
|
|
|
|
|
|
|
|
# If the value of a user's "uid" (or similar) property is not their email
|
|
|
|
# address, specify the domain to append here.
|
2013-11-22 22:58:22 +01:00
|
|
|
LDAP_APPEND_DOMAIN = ADMIN_DOMAIN
|
2013-11-21 01:30:20 +01:00
|
|
|
|
2013-11-22 22:58:22 +01:00
|
|
|
# This map defines how to populate attributes of a Zulip user from LDAP.
|
2013-11-21 01:30:20 +01:00
|
|
|
AUTH_LDAP_USER_ATTR_MAP = {
|
|
|
|
# Populate the Django user's name from the LDAP directory.
|
|
|
|
"full_name": "cn",
|
|
|
|
}
|
|
|
|
|
2013-11-14 05:25:45 +01:00
|
|
|
# The following secrets are randomly generated during the install
|
|
|
|
# process, are used for security purposes, and should not be shared
|
|
|
|
# with anyone.
|
|
|
|
#
|
|
|
|
# PLEASE DO NOT CHANGE THEM WITHOUT INSTRUCTIONS FROM ZULIP SUPPORT
|
2013-10-25 21:19:30 +02:00
|
|
|
CAMO_KEY = ''
|
|
|
|
SECRET_KEY = ''
|
|
|
|
HASH_SALT = ''
|
|
|
|
RABBITMQ_PASSWORD = ''
|
|
|
|
AVATAR_SALT = ''
|
|
|
|
SHARED_SECRET = ''
|