Skip to content
Snippets Groups Projects
Select Git revision
  • d1e50f2ef6724f8e1d782817dd94e4f1c03f5820
  • master default protected
  • v3-modify-mail
  • snyk-fix-207483a1e839c807f95a55077e86527d
  • translations_3b5aa4f3c755059914cfa23d7d2edcde_ru
  • translations_6e4a5e377a3e50f17e6402264fdbfcc6_ru
  • translations_3b5aa4f3c755059914cfa23d7d2edcde_fa_IR
  • translations_en-yml--master_fa_IR
  • snyk-fix-7d634f2eb65555f41bf06d6af930e812
  • translations_en-yml--master_ar
  • translations_3b5aa4f3c755059914cfa23d7d2edcde_el
  • jfederico-patch-1
  • v2
  • v3
  • v1
  • release-3.1.0.2
  • release-3.1.0.1
  • release-3.1.0
  • release-2.14.8.4
  • release-3.0.9.1
  • release-3.0.9
  • release-3.0.8.1
  • release-2.14.8.3
  • release-3.0.8
  • release-3.0.7.1
  • release-2.14.8.2
  • release-3.0.7
  • release-3.0.6.1
  • release-3.0.6
  • release-3.0.5.4
  • release-3.0.5.3
  • release-2.14.8.1
  • release-3.0.5.2
  • release-3.0.5.1
  • release-3.0.5
35 results

sample.env

Blame
  • user avatar
    farhatahmad authored and Jesus Federico committed
    02c0d577
    History
    sample.env 6.31 KiB
    # 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:v2 bundle exec rake secret
    #
    SECRET_KEY_BASE=
    
    # The endpoint and secret for your BigBlueButton server.
    # Set these if you are running GreenLight on a single BigBlueButton server.
    # You can retrive these by running the following command on your BigBlueButton server:
    #
    #   bbb-conf --secret
    #
    BIGBLUEBUTTON_ENDPOINT=
    BIGBLUEBUTTON_SECRET=
    
    # Google Login Provider (optional)
    #
    # For in-depth steps on setting up a Google Login Provider, see:
    #
    #   http://docs.bigbluebutton.org/install/greenlight-v2.html#google-oauth2
    #
    # The GOOGLE_OAUTH2_HD variable is used to limit sign-ins to a particular set of Google Apps hosted
    # domains. This can be a string with separating commas such as, 'domain.com, example.com' or
    # a string that specifies a single domain restriction such as, 'domain.com'.
    # If left blank, GreenLight will allow sign-in from all Google Apps hosted domains.
    GOOGLE_OAUTH2_ID=
    GOOGLE_OAUTH2_SECRET=
    GOOGLE_OAUTH2_HD=
    
    # Twitter Login Provider (optional)
    #
    # For in-depth steps on setting up a Twitter Login Provider, see:
    #
    #   http://docs.bigbluebutton.org/install/greenlight-v2.html#twitter-oauth2
    #
    TWITTER_ID=
    TWITTER_SECRET=
    
    # Microsoft Office365 Login Provider (optional)
    #
    # For in-depth steps on setting up a Office 365 Login Provider, see:
    #
    #   http://docs.bigbluebutton.org/install/greenlight-v2.html#office365-oauth2
    #
    OFFICE365_KEY=
    OFFICE365_SECRET=
    OFFICE365_HD=
    
    # LDAP Login Provider (optional)
    #
    # You can enable LDAP authentication by providing values for the variables below.
    # Configuring LDAP authentication will take precedence over all other providers.
    # For information about setting up LDAP, see:
    #
    #   http://docs.bigbluebutton.org/install/greenlight-v2.html#ldap-auth
    #
    #   LDAP_SERVER=ldap.example.com
    #   LDAP_PORT=389
    #   LDAP_METHOD=plain
    #   LDAP_UID=uid
    #   LDAP_BASE=dc=example,dc=com
    #   LDAP_BIND_DN=cn=admin,dc=example,dc=com
    #   LDAP_PASSWORD=password
    LDAP_SERVER=
    LDAP_PORT=
    LDAP_METHOD=
    LDAP_UID=
    LDAP_BASE=
    LDAP_BIND_DN=
    LDAP_PASSWORD=
    
    # Set this to true if you want GreenLight to support user signup and login without
    # Omniauth. For more information, see:
    #
    #   http://docs.bigbluebutton.org/install/greenlight-v2.html#in-application-greenlight
    #
    ALLOW_GREENLIGHT_ACCOUNTS=true
    
    # To enable reCaptcha on the user sign up, define these 2 keys
    # You can obtain these keys by registering your domain using the following url:
    #
    #  https://www.google.com/recaptcha/admin
    #
    RECAPTCHA_SITE_KEY=
    RECAPTCHA_SECRET_KEY=
    
    # Set this to true if you want GreenLight to send verification emails upon
    # the creation of a new account
    #
    #   ALLOW_MAIL_NOTIFICATIONS=true
    #
    # The notifications are sent using sendmail, unless the SMTP_SERVER variable is set.
    # In that case, make sure the rest of the variables are properly set.
    #
    #   SMTP_SERVER=smtp.gmail.com
    #   SMTP_PORT=587
    #   SMTP_DOMAIN=gmail.com
    #   SMTP_USERNAME=<youremail@gmail.com>
    #   SMTP_PASSWORD=<yourpassword>
    #   SMTP_AUTH=plain
    #   SMTP_STARTTLS_AUTO=true
    #
    SMTP_SERVER=
    SMTP_PORT=
    SMTP_DOMAIN=
    SMTP_USERNAME=
    SMTP_PASSWORD=
    SMTP_AUTH=
    SMTP_STARTTLS_AUTO=
    
    # Specify the email address that all mail is sent from
    SMTP_SENDER=
    
    # Prefix for the applications root URL.
    # Useful for deploying the application to a subdirectory, which is highly recommended
    # if deploying on a BigBlueButton server. Keep in mind that if you change this, you'll
    # have to update your authentication callback URL's to reflect this change.
    #
    #   The recommended prefix is "/b".
    #
    RELATIVE_URL_ROOT=/b
    
    # Specify which settings you would like the users to configure on room creation
    # or edit after the room has been created
    # By default, all settings are turned OFF.
    #
    # Current settings available:
    #   default-client: Room owners can decide between the Flash Client and the HTML5 Client for a room
    #   mute-on-join: Automatically mute users by default when they join a room
    ROOM_FEATURES=default-client,mute-on-join
    
    # Specify the maximum number of records to be sent to the BigBlueButton API in one call
    # Default is set to 25 records
    PAGINATION_NUMBER=25
    
    # Specify the maximum number of rows that should be displayed per page for a paginated table
    # Default is set to 25 rows
    NUMBER_OF_ROWS=25
    
    # Specify if you want to display the Google Calendar button
    #   ENABLE_GOOGLE_CALENDAR_BUTTON=true|false
    ENABLE_GOOGLE_CALENDAR_BUTTON=
    
    # Set the application into Maintenance Mode
    #
    # Current options supported:
    # full: Renders an error page that does not allow users to access any of the features in the application
    # readonly: Sets the database to readonly mode, which allows users to use actions that dont write to the database
    # false: Application runs normally
    MAINTENANCE_MODE=false
    
    # Comment this out to send logs to STDOUT in production instead of log/production.log .
    #
    # RAILS_LOG_TO_STDOUT=true
    #
    # When using docker-compose the logs can be sent to an centralized repository like PaperTrail
    # just by using the built in driver. Make sure to add to docker-compose.yml the next lines:
    #
    #     logging:
    #      driver: $LOG_DRIVER
    #      options:
    #        syslog-address: $LOG_ADDRESS
    #        tag: $LOG_TAG
    #
    # And set this variables up:
    #
    # LOG_DRIVER=syslog
    # LOG_ADDRESS=udp://logs4.papertrailapp.com:[99999]
    # LOG_TAG=greenlight.example.com:v2
    #
    # Check docker-compose and papertrail documentation for encrypting and
    # protecting access to the log repository.
    # https://docs.docker.com/config/containers/logging/syslog/#options
    # https://help.papertrailapp.com/kb/configuration/encrypting-remote-syslog-with-tls-ssl/
    #
    # For sending logs to a remote aggregator enable these variables:
    #
    # RAILS_LOG_REMOTE_NAME=logxx.papertrailapp.com
    # RAILS_LOG_REMOTE_PORT=9999
    # RAILS_LOG_REMOTE_TAG=greenlight
    #
    # Force SSL
    #
    # ENABLE_SSL=true
    
    # Database settings
    #
    # Greenlight may work out of the box with sqlite3, but for production it is recommended to use postgresql.
    # In such case, these variables must be included.
    #
    # DB_ADAPTER=postgresql
    # DB_HOST=postgres.example.com
    # DB_NAME=greenlight_production
    # DB_USERNAME=postgres
    # DB_PASSWORD=password
    #
    # For deployments based on the docker-compose script also included, the HOST should be set with the Docker container id.
    #
    # DB_ADAPTER=postgresql
    # DB_HOST=db
    # DB_NAME=greenlight_production
    # DB_USERNAME=postgres
    # DB_PASSWORD=password