Skip to main content
WordPress Development

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • My primary concern is not so much in the changes that people may make to the pages - I've structured the theme in such a way that a situation like that happening could very rarely happen unless someone has access to the raw PHP files. The biggest concern here is if the server crashes, we want to have a backup server so that we can still operate as a company. Commented Apr 19, 2017 at 21:55
  • Hi Trenton, I understand, and still think the "versioning" approach would provide the best answer. Ultimately you could deploy from the repository (I urge you to check out the likes of beanstalkapp.com to make it easier) automatically to a staging server, and two production servers. If a server goes down you could simply switch to another box... even that can be automated with some kind of DNS monitoring and switch-over routines. You'd also have to sync databases, but that can be easily achieved using cron and rysnc, same goes for wp-content Commented Apr 20, 2017 at 5:59
  • I think this would be a great solution in many other situations, but for the sake of ease in my case, it just doesn't quite do the job. I appreciate your help, though. Commented May 2, 2017 at 21:02