texas-justice-initiative / website

GNU General Public License v2.0
3 stars 1 forks source link

Database Migrations / Environment Consistency (prod, staging, local) #108

Open ifsimicoded opened 6 years ago

ifsimicoded commented 6 years ago

We need a better strategy to ensure our environments are in sync for better testing. The first pain-point I felt was having the donation page exist locally exactly the way it would in staging. This would require a better procedure (maybe automated) for handling database changes. So if someone were to create a page locally in the database, that database change could be pushed to staging. And then when reviewed there, it could be pushed to production. Similarly I could update my local environment to reflect the staging environment.

EvaRuthM commented 6 years ago

I'm wondering if any of this will be addressed in the automation tasks that Aiden is working on?

On Sun, Oct 28, 2018 at 5:27 PM ifsimicoded notifications@github.com wrote:

We need a better strategy to ensure our environments are in sync for better testing. The first pain-point I felt was having the donation page exist locally exactly the way it would in staging. This would require a better procedure (maybe automated) for handling database changes. So if someone were to create a page locally in the database, that database change could be pushed to staging. And then when reviewed there, it could be pushed to production. Similarly I could update my local environment to reflect the staging environment.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/texas-justice-initiative/website/issues/108, or mute the thread https://github.com/notifications/unsubscribe-auth/AQID-8SzhtJtaUkUuF7AQktmZPjWhaaLks5upi9qgaJpZM4X-OL- .

-- (210) 422-9737 cell Twitter http://www.twitter.com/evaruth Portfolio http://muckrack.com/EvaRuth/portfolio Texas Justice Initiative http://www.texasjusticeinitiative.org