search

amazon-archives / awsmobile-cli

CLI experience for Frontend developers in the JavaScript ecosystem.
Apache License 2.0
142 stars 35 forks source link

Parallel development for backend #135

Open thelinuxkid opened 6 years ago

thelinuxkid commented 6 years ago

This is related to another issue I just posted. Because I haven't been able to test the backend locally, it's difficult for two developers to collaborate on the same backend -- one developer's changes override the other's when both do an awsmobile push. It's similar to working with git but on a single branch. What are the best practices in this case?

UnleashedMind commented 6 years ago

I would suggest to keep two environments, one for dev and test, and one for production. The dev and test environment is expected to be unstable. And before you push, do a pull and compare the code in #current-backend-info folder with your local development in the backend folder, because your coworker might have changed the cloud. Then when everything is tested fine, update the backend folder of the project that's linked to the production environment, and do a push.

dan1elhughes commented 6 years ago

Is there a tutorial which explains this workflow? Right now we're doing local development on the production database, as the aws-exports gives us the prod data.