You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2020. It is now read-only.
I realized that I left out the USE_LDAP environment variable when I set up .env.example. We're also tracking the .env file in Git, which isn't really good practice. Therefore, we should do the following:
The last two point occurred to me as I thought about removing the .env file... to be honest, we shouldn't really need to copy both a secrets.yml file and a .env file to run the app locally. I'm happy to use a Rails secret for both instead of the raw environment variables, any thoughts?
The text was updated successfully, but these errors were encountered:
Ok, just finishing up the removal of .env from Git; from now on new users should copy the .env.example file and uncomment the example lines as desired (for LDAP and CAS). Other configuration parameters will be defined in secrets.yml.
I realized that I left out the
USE_LDAP
environment variable when I set up.env.example
. We're also tracking the.env
file in Git, which isn't really good practice. Therefore, we should do the following:USE_LDAP
in.env.example
USE_LDAP
in the configuration wiki pagedocument LDAP stuff in the Heroku wiki page.env
moveUSE_LDAP
tosecrets.yml
?moveCAS_AUTH
tosecrets.yml
?The last two point occurred to me as I thought about removing the
.env
file... to be honest, we shouldn't really need to copy both asecrets.yml
file and a.env
file to run the app locally. I'm happy to use a Rails secret for both instead of the raw environment variables, any thoughts?The text was updated successfully, but these errors were encountered: