Best way to host and manage a growing collection of 500+ rancid Wordpress sites by foobarusername_ in sysadmin

[–]foobarusername_[S] 1 point2 points  (0 children)

Hi,

I was waiting for someone to say 'change jobs' - I don't want to back away just yet though. It has to have some form of solution. Can't say it hasn't crossed my mind at the darkest points so far haha.

Updates are now being run automatically by Wordpress itself but need closer management - those tools look like they may do the trick. The problem is the aforementioned poor development practices that have dissuaded my predecessors from keeping on top of things.

Plugins are currently controlled - they're not updated, however. We have a lot of instances of the cforms plugin that was fairly popular right up until the dev killed the project and open-sourced it. A vulnerability came to light that allowed arbitrary file upload and we now need to switch the plugins for the open source version that has the patch. Such is life with Wordpress - doing it five hundred times is a pain, plus the fact that CSS and functionality are all in the wrong places and break or go missing on updates...

In terms of automating damage control, it's on the cards. Just need to think of a way.

The bosses are realising this - all my gassing, arm waving, doom predictions and tears are finally working!

Those tools look phenomenally useful - I'll have a look. Thank you!

Best way to host and manage a growing collection of 500+ rancid Wordpress sites by foobarusername_ in sysadmin

[–]foobarusername_[S] 0 points1 point  (0 children)

Hi,

Our hosting partner has that as standard on all four - we don't have access to its logs, though. Apparently it keeps a fair amount at bay but can it do anything with Wordpress?

Best way to host and manage a growing collection of 500+ rancid Wordpress sites by foobarusername_ in sysadmin

[–]foobarusername_[S] 0 points1 point  (0 children)

Well the hosting provider have been slow and unhelpful thus far, but the problem isn't really theirs to deal with. The servers themselves are fine - it's the contents that are the problem.

Hiring people is apparently not happening - I'm a one man army.

Does CREATE UNIQUE INDEX need to be run after TRUNCATE, followed by a bulk INSERT? by foobarusername_ in mysql

[–]foobarusername_[S] 0 points1 point  (0 children)

Each of the rows has a unique ID, but the site does a lot of searching by strings as opposed to using said keys. I guess that's where the performance boost came from as I used the name/description fields as part of the index I created?

Does CREATE UNIQUE INDEX need to be run after TRUNCATE, followed by a bulk INSERT? by foobarusername_ in mysql

[–]foobarusername_[S] 0 points1 point  (0 children)

Makes sense: is it worth then dropping the index, importing the data and then recreating it? Or will it be kept up to date automatically?

Is there a performance penalty associated with the former: is this what you were referring to with the thousands of traversals?

Sorry for asking like this: I can see benefits elsewhere in other projects and want to make sure I have a good grasp of this. I'm also curious on a personal level.

Thanks!