forked from External/greenlight
89 lines
2.8 KiB
Plaintext
89 lines
2.8 KiB
Plaintext
# Step 1 - Create a secret key for rails
|
|
#
|
|
# You can generate a secure one through the Greenlight docker image
|
|
# with with the command
|
|
#
|
|
# docker run --rm bigbluebutton/greenlight rake secret
|
|
#
|
|
SECRET_KEY_BASE=
|
|
# Step 2 - Enter credentials for your BigBlueButton Server
|
|
#
|
|
# The endpoint and secret from your bigbluebutton server. To get these values, run
|
|
# the following command on your BigBlueButton server
|
|
#
|
|
# bbb-conf --secret
|
|
#
|
|
# and uncomment the following two variables
|
|
#BIGBLUEBUTTON_ENDPOINT=
|
|
#BIGBLUEBUTTON_SECRET=
|
|
|
|
# Twitter Login Provider (optional)
|
|
#
|
|
# You will need to register the app at https://apps.twitter.com/
|
|
# For the callback URL use 'http://<your hostname:port>/auth/twitter/callback'
|
|
# Once registered copy the ID and Secret here
|
|
#
|
|
TWITTER_ID=
|
|
TWITTER_SECRET=
|
|
|
|
# Google Login Provider (optional)
|
|
#
|
|
# You will need to register for at https://console.developers.google.com/apis/credentials
|
|
# Select Oauth client ID -> web application
|
|
# For the callback URL use 'http://<your hostname:port>/auth/google/callback'
|
|
# Once registered copy the ID and Secret here
|
|
#
|
|
GOOGLE_OAUTH2_ID=
|
|
GOOGLE_OAUTH2_SECRET=
|
|
|
|
# If "true", GreenLight will register a webhook callback for each meeting
|
|
# created. This callback is called for all events that happen in the meeting,
|
|
# including the processing of its recording. These events are used to update
|
|
# the web page dynamically as things happen in the server.
|
|
# If not "true", the application will add a metadata to the meetings with this same
|
|
# callback URL. Scripts can then be added to BigBlueButton to call this callback
|
|
# URL and send specific events to GreenLight (e.g. a post publish script to warn
|
|
# the application when recordings are done).
|
|
GREENLIGHT_USE_WEBHOOKS=false
|
|
|
|
# Slack Integration (optional)
|
|
#
|
|
# You will need to register an incoming-webhook for your slack channel
|
|
# in order for GreenLight to post to it. You can do this by going
|
|
# to https://slack.com/apps/A0F7XDUAZ-incoming-webhooks, selecting your
|
|
# team and then selecting "Add Incoming WebHooks integration" on the
|
|
# desired channel. You will then need to paste the webhook below.
|
|
#
|
|
SLACK_WEBHOOK=
|
|
SLACK_CHANNEL=
|
|
|
|
# Landing Background (optional)
|
|
#
|
|
# Supply a URL to an image to change the landing background. If no
|
|
# URL is provided GreenLight will use a default image. If you
|
|
# supply a path that does not lead to an image, no landing image
|
|
# will appear.
|
|
#
|
|
LANDING_BACKGROUND=
|
|
|
|
# SMTP Mailer
|
|
#
|
|
GREENLIGHT_MAIL_NOTIFICATIONS=true
|
|
GREENLIGHT_DOMAIN=localhost-lxc.org
|
|
SMTP_FROM=youremail@gmail.com
|
|
SMTP_SERVER=smtp.gmail.com
|
|
SMTP_PORT=587
|
|
SMTP_DOMAIN=gmail.com
|
|
SMTP_USERNAME=youremail@gmail.com
|
|
SMTP_PASSWORD=yourpassword
|
|
# SMTP_TLS=false
|
|
# SMTP_AUTH=login
|
|
# SMTP_STARTTLS_AUTO=true
|
|
|
|
# Prefix for the application's root URL
|
|
# Useful for deploying the application to a subdirectory
|
|
#
|
|
# default is '/b' (recommended)
|
|
#
|
|
#RELATIVE_URL_ROOT=/b
|