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

Staging environment #77

Open
wdanfort opened this issue Sep 13, 2020 · 1 comment
Open

Staging environment #77

wdanfort opened this issue Sep 13, 2020 · 1 comment

Comments

@wdanfort
Copy link
Collaborator

Will be helpful to have a staging environment as more people use service and features become more complex to avoid major service disruptions and breaking changes. Potentially we can use our original Twilio number?

@ianhoffman
Copy link
Collaborator

Hmm. A few things about this:

  • A staging env will cost money since we'll need to double pay for infra in AWS. So expect roughly 2x our current monthly AWS costs — an extra $40 a month at least.
  • Most of the bugs we'd prevent in a staging env can also be prevented via local testing. We're such a small operation, I think it's totally acceptable to just have a local dev env and a prod env ATM.

So I'd recommend tabling this for now.

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

No branches or pull requests

2 participants