Dear, in these days developers ask for a "staging" installation of the "production" website. Something like pointed bu a third level domain like: Production: myproductiondomain.com (with his own database) Staging: staging.myproductiondomain.com (with his own database)With a tool that by request sync the data from the two installation (both files and db). Exist any best-practice to do that with ISPConfig 3 or case study? Thank you
If no changes are done in the production site, then this is doable. Erasing production site files and db, then copy staging files and db. If changes can be made also to production site, things get complicated.
I would just add a second website with staging.myproductiondomain.com in ISPConfig for the staging site. Most web design agencies that maintain larger websites use git today, so they simply check out the site with git to the staging site, test it, and then check it out to the production site when the test was successful.
