With this Workflow you can manage most of the standard sites that are not often modified once they are live, typical use cases:
- Corporate/informative websites
- Landing Pages
- Blogs with an external comment system (disqus, discourse)
- Ecommerce websites
- News sites
- Blogs with internal (database stored) comment systems
This is the simplest possible workflow, where all phases are identical constantly. That is, the content of Develop, Demo and Production has to be always the same.
That means that when you push from one phase to the next, everything is replaced, both database contents and files.
In order to avoid inconsistencies or overwriting data whilst updating/upgrading/modifying your website in the Develop environment, the recommended sync strategy for this workflow is:
- Freeze/lock the Production Site: The site is still accessible for anonymous users, but it cannot be modified by administrators or any other type of website users
- Dump the Production version to the Develop environment to make sure the content is exactly the same
- Perform modifications/upgrades safely in the Develop environment
- Push the Develop version to the Demo phase to make sure everything works properly in the Live Hosting and/or get the approval of the client for the new modifications
- When everything works properly, publish the website again by pushing the Demo version to the Production phase. This environment will get automatically "unfrozen/unlocked" when pushed from the Demo phase, so it can be modified again by the website's users