Molly I think debugging on production sounds not right at all.
What we do is that commits should first pass to our staging env (that totally mimicks our production).
Then we try things there (automated and manually), and if everything seems right we hit the button to deploy on production too.
Yes, Docker and ElasticBeanstalk here helps a lot to create super simple maintainable pipeline
We also use that staging env for debugging like once we had a weird issue with Celery and AWS SQS, took us a bit of time but we never debugged on production.
We are hoping to get a staging environment up and running once we have containerized our application. Hopefully, that will cover some of the differences that still exist between our vagrants and production.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Molly I think debugging on production sounds not right at all.
What we do is that commits should first pass to our staging env (that totally mimicks our production).
Then we try things there (automated and manually), and if everything seems right we hit the button to deploy on production too.
We also use that staging env for debugging like once we had a weird issue with Celery and AWS SQS, took us a bit of time but we never debugged on production.
Thanks for the thoughtful feedback!
We are hoping to get a staging environment up and running once we have containerized our application. Hopefully, that will cover some of the differences that still exist between our vagrants and production.