.env File

tl;dr - Ask Frank for the .env file. Place it in the late/ folder and MAKE SURE IT IS NAMED .env AND NOT JUST env. This contains all our passwords and API keys.

---

Because LATE connects to a database, Google APIs, and other similar services, there are many passwords and secret keys that cannot be included in the public repository but are required for LATE to run. All of these are kept in one place, in a file named .env in the root folder. Because the information in the file is super sensitive and private, it is not publicly included in the repository and the repository ignores it so it never gets pushed to GitHub. You will not find this anywhere publicly (hopefully!).

Only LATE team members have the .env file and will give it to you when you need it. You are not to share it or anything in it with anyone.

Sometimes new passwords/secrets are needed when new features are added, Frank will alert the team about these and distribute the updated .env.

If you want to have your own custom version of LATE running locally, you'll need to create your own env file and supply your own keys.

Here is an example of the format from .env.example:

CAS_SERVICE_URL=http://localhost:9000
HOST=0.0.0.0
PORT=1234
MONGODB_URI=XXXXXXXXXXXXXXXXXXXXXXXX
TWILIO_ACCOUNT_SID=XXXXXXXXXXXXXXXXXXXXXXXX
TWILIO_AUTH_TOKEN=XXXXXXXXXXXXXXXXXXXXXXXX
TWILIO_PHONE_NUMBER=XXXXXXXXXXXXXXXXXXXXXXXX
DISCORD_CLIENT_ID=XXXXXXXXXXXXXXXXXXXXXXXX
DISCORD_CLIENT_SECRET=XXXXXXXXXXXXXXXXXXXXXXXX
DISCORD_BOT_TOKEN=XXXXXXXXXXXXXXXXXXXXXXXX
DISCORD_BOT_COMMAND_PREFIX=!
SENDGRID_API_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXX