[CentOS] Using CentOS Wordpress rpms

[John Hinton]

On 11/12/2013 9:44 AM, Brian Mathis wrote:
> On Mon, Nov 11, 2013 at 10:59 PM, Max Pyziur <pyz at brama.com> wrote:
>
>> On Tue, 12 Nov 2013, Keith wrote:
>> [...]
>>   >
>>> I always install from the latest tarball from the WP site, as it's the
>>> latest at the time of installation. With regards to WP updates and
>>> versions, this is generally performed with it's own built in
>>> updating/upgrading mechanism which is the first thing you should check
>>> or do after install and on an ongoing basis - IMHO anyway.
>> Makes sense.
>>
>> So what are the point of having RPMs if you can't apply it server-wide
>> across multiple sites?
>>
>> MP
>>
>
>
> Maybe the packages are meant for a different usage pattern than yours?
>
> Packaging anything, but particularly web apps, involves making tradeoffs.
> For most people, package defaults provide a basic set of functionality
> (which can be adequate for most people), but there are some cases where a
> power user might have need to install them with other settings.
>
> Your usage pattern as a hosting provider is on the "power user" end of the
> spectrum, and you should probably be using the tar file or even creating
> your own custom rpms so you can set it up as you need it.
>
>
> ❧ Brian Mathis
> _______________________________________________
>
To my knowledge, there has always been a 'central WordPress install' 
method. I 'assume' that is what this RPM does?

Aside from that... Plugin hell! The automated WP updates is really new 
and I am betting will break sites 'automatically'. We turn this feature 
off for the moment.

The issue is plugins. Most people run some plugins on their WP 
installations and some people run dozens. Each of these can be website 
critical, or IOW, if they don't work the site is totally broken. This 
happens far too often during an update to WordPress.

So, our method has been an extra fee added to hosting WP sites, so that 
we can monitor and do the upgrades, so we know they are done. We work 
with the client if there are conflicts with plugins. We do the update 
and then give the website a once over to try to find any broken 'features'.

It all depends on how kind you wish to be with your customers. (but I do 
hope the automated part can actually work... perhaps in the future at 
least?)

Best,
John Hinton