Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unify envs #895

Closed
compwron opened this issue Oct 1, 2020 · 4 comments · Fixed by #970
Closed

unify envs #895

compwron opened this issue Oct 1, 2020 · 4 comments · Fixed by #970
Assignees

Comments

@compwron
Copy link
Collaborator

compwron commented Oct 1, 2020

What type of user is this for? volunteer/supervisor/admin/all
don't use non-production.rb files for diff envs, to avoid making duplicate changes and catching them.

Description
Make sure no one can send mail from staging environment.

@littleforest
Copy link
Collaborator

@compwron you mentioned that emails should not go out on staging, but I'm not seeing anywhere in the configuration file nor in the code that prohibits that. Can you point me where that would be? Or were you saying that feature needs to be set up?

@compwron
Copy link
Collaborator Author

compwron commented Oct 2, 2020

@littleforest yes, I meant "should" as in "the way I want it to be" not as in "the way I believe it currently is" sorry for the confusion.

@littleforest
Copy link
Collaborator

@compwron thanks! I'm not seeing any differences in configuration between staging and production currently -- would that be the only change? Also, I'm assuming QA should be able to send emails?

@compwron
Copy link
Collaborator Author

compwron commented Oct 4, 2020

@littleforest agreed, staging and prod are intended to be the same right now. QA currently does not have API keys for sending emails set up in heroku (intentionally, to prevent spam risk) but it is ok to have the rails configurations assume that sending emails ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants