production settings

sample.env

@@ -1,10 +1,15 @@
-# If set to true, GreenLight will attempt to fetch the endpoint and secret from the credentials
-# endpoint by passing it the users provider. This is useful when launching into GreenLight from
-# and external service with a customer provider (who may have different credentials).
+# This is a sample of the environment variables you will need
+# To use, copy this file to .env `cp sample.env .env`
+
+# 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=
 
-# It is also worth noting that ALL Omniauth providers resolve to "greenlight" before being sent.
-# If you are configuring GreenLight for use with a single BigBlueButton server, set this to false.
-USE_LOADBALANCED_CONFIGURATION=false
 
 # The endpoint and secret for your BigBlueButton server.
 # Set these if you are running GreenLight on a single BigBlueButton server.
@@ -15,12 +20,6 @@ USE_LOADBALANCED_CONFIGURATION=false
 BIGBLUEBUTTON_ENDPOINT=
 BIGBLUEBUTTON_SECRET=
 
-# The endpoint and secret for your Loadbalancer server.
-# Set these ONLY IF you are running BigBlueButton under a loadbalanced configuration.
-# GreenLight will use these credentials to retrieve provider based server credentials.
-LOADBALANCER_ENDPOINT=
-LOADBALANCER_SECRET=
-
 # Google Login Provider (optional)
 #
 # For in-depth steps on setting up a Google Login Provider, see:
@@ -46,4 +45,4 @@ TWITTER_SECRET=
 # Set this to true if you want GreenLight to support user signup and login without
 # Omniauth. This will allow users to create an account at www.hostname.com/signup
 # and use that account to fully interact with GreenLight.
-ALLOW_GREENLIGHT_ACCOUNTS=false
+ALLOW_GREENLIGHT_ACCOUNTS=false