We have a fairly simple Django-based website for doing CRUD operations. I've been doing testing and development locally and then checking out releases and database schema changes onto the live server once testing is done. We've recently run into a problem when releasing some types of changes. Imagine the following sequence of events:
How do other sites handle these kinds of problems? My ideas:
Thoughts?
The two most common ways of updating your website are by: creating and editing webpages on your computer and then transferring them to the GreenNet webserver using FTP or. submitting new content for your website through an online web form that you access using a content management system.
Still, updating content can be a difficult process for some business owners. Many web design companies build websites that make it complicated to change content. They require the customer to learn a complex array of shortcodes or pay a monthly fee for a set number of updates and changes.
Changes to a published API (or UI, in this case) is always tricky. If possible, preserve backwards compatibility. For most forms, I would reckon that the functionality wouldn't change between versions. You might add or remove a field or two, but that would be handled by the form validation on the backend. That's essentially what you're describing in your step 4. I don't really consider that much of a problem; Runtime errors happen from time to other - As long as your application handles it gracefully and informs the user of the problem, then no issue really.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With