[wp-hackers] Clustering WordPress
martin at lazarov.bg
Mon Aug 20 22:07:46 UTC 2012
/wp-admin/ can be forced to be only on one server. So when you make
change on this server all other copies are replicated (for example
On Tue, Aug 21, 2012 at 12:53 AM, Brian Layman
<wp-hackers at thecodecave.com> wrote:
> I've written plugins that disable all of those messages and version checks
> (but that was harder to do than you might think and I'm not sure I like my
> final result).
> However, it can also just be handled as a training issue. Having only a
> very limited number of admins able to take those actions helps a lot. After
> all, it's best if admin accounts are used only for those types of
> administrative actions. Lower level accounts should be used for your
> posting needs.
> Monitoring what's changed on your servers is a good idea in any case. A VCS
> can show you that easily. You just need to commit the changes you approve.
> Brian Layman
> On 8/20/2012 5:43 PM, John Elliot wrote:
>> On 2012-08-21 06:20, Brian Layman wrote:
>>> Good stuff:
>> Thanks for sharing that.
>> Initially I put a few of my WordPress installations in svn like Mark
>> recommends and installed them on the server by checking them out. Then I
>> used the admin interface to upgrade and it corrupted my svn working copy
>> so I couldn't check the changes back in to svn.
>> Also on another attempt one of my users used the admin tool to change
>> his theme and the files got out of sync with the repo then too.
>> So now I have a bunch of WordPress installations that initially were in
>> svn and are now just corrupt and useless svn working copies.
>> If you check your WordPress installation into a VCS what is the
>> recommended strategy for upgrading it? Can you disable administrative
>> functions such as in-browser upgrades, installing themes, upgrading
>> plugins, etc. in the config file somehow? Is that what you're supposed
>> to do?
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers