Deployment best-practices in Apex

Viewed 36

I have two instances of Apex, Development and Production.

My current process involves making updates on Development, exporting the app and then importing and overwriting the app on Production. But if I make any schema changes, I am also having to go into the live production database and make those same changes as well.

Doing these changes on a live database is surely bad practice. I've used with frameworks in the past that have elegant database migration tools that allow for rollback, etc. And provide a lot of peace of mind.

Does anything like this exist for Apex? Or is this the only way of deploying between separate instances?

Thanks!

0 Answers
Related