-
Notifications
You must be signed in to change notification settings - Fork 57
Configuration
In order to configure a deployment of Reservations, there are a number of environment variables that need to be set. We're using dotenv and dotenv-deployment to simulate the presence of environment variables for Rails in situations where they aren't actually defined in the system, but these do not need to be used. The following document details the environment variables that need to be set and how they are used.
The presence of this environment variable determines whether or not to use CAS authentication (if it is present / defined to any value, CAS authentication is used). The decision of whether or not to use it should be made even before the initial setup for the application as it will modify the creation of the first user / superuser. The switching of authentication methods from CAS to e-mail/password is not supported by Reservations (for more information see here).
This environment variable defines the base url of the CAS authentication server (e.g. https://secure.its.yale.edu/cas/). It is only necessary if using CAS authentication.
This environment variable stores the secret key used by Devise to generate random tokens. It should be set to a random token which can be generated by rake secret (produces a pseudo-random 128-character hexidecimal string).
This environment variable stores the "pepper" used by devise to help generate encrypted passwords. It should be set to a random token Like DEVISE_SECRET_KEY. It is only necessary if using e-mail / password authentication.