: Can I set up two WordPress servers; a Read-Write server on a local Intranet which is then synced to a Read-Only public Internet server? Background I've got a website set up running WordPress.
Background
I've got a website set up running WordPress. I have multiple people who need login access to manage the software. They all access the website from the same physical location, and I have access to a company intranet.
Standard Practice (?)
Normally, they would log in directly to the website, and their edits would be made to the live database.
My Goals
I want the public website to be inaccessible as much as possible. I want zero WordPress logins.
I want data duplication, in case the live server goes down.
Plan
I want to set up a two part system, with an internal copy of the website that is hosted on a company intranet, accessible only to users who are on the internal network. They will make edits there.
I am planning then to use MySQL Master-Slave replication to mirror the data from the intranet copy (Master) to the live copy (Slave), with some changes on the live copy, such as disabling user logins completely.
Question
Is this a good plan? Or is there a better option? (I am a front end dev who has been thrown into DB management, so there are probably lots of things I'm not aware of.)
More posts by @Yeniel560
3 Comments
Sorted by latest first Latest Oldest Best
Answer
Technically it's possible, but it way too complicated. There are better ways.
Some Reasons
Some issues that I ran into when trying this:
You have to sync both the DB files, AND the physical "WP Uploads" folder at the same time, anytime a change is made.
You'd have to figure out a way to have author attribution on the front end, on the Live server that doesn't have user accounts. Only way that I can think to do this is to mirror the Users table with a CTP, called UsersFake. Have a hidden Metadata text field on Posts, which copies the Post's Author. Then use the FakeUsers to create the front end "Author" section at the end of each blog post. I played around with it a bit but it got really complicated really fast.
Basically, it's not worth it.
What I Did Instead
The direction I went instead is to combine IP locking for logins, with a snapshot backup system on the live server.
I guess it is possible. This answer may be helpful. All you then need to do on the public instance is find a checkbox on Settings > General that says “Anyone can register”. Uncheck this. When someone accesses the login page, there will no longer be a “Register” link they can use. Then you will probably just lock out the default admin account if so desired.
Works much of the same way. It's just you can have two unique domains pointing at the same server, and the server will have DNS rules to direct incoming traffic to the correct part of the server. On the server folder side, it would look almost identical to what you have set up, with different WordPress sites in different sub directories.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.