How to update TKL Wordpress v13 to v14?

I'm new to Linux and Turnkey. I installed a TKL Wordpress v13 appliance on a VMware 6.0 platform. I've done some development work on it and provided for some user access to import a Wordpress site. I've setup TKLBAM.

I'd like to upgrade to TKL Wordpress v14 without losing the work I've done on v13. I can't find instructions for how to do that, though I can't imagine they don't exist, and it's probably quite simple. Can someone just point me to them? Thanks!

~David

Replies (3)

Hi David

Reply 1 2015-12-14

TKLBAM should take care of transferring your data. Although you will need to make some tweaks to your site file for Apache 2.4 (as included in v14.0). The main one is that it needs to explicitly be a .conf file.

What I would recommend is doing a TKLBAM backup, then create a new v14.0 server and restore your data to that. Once you've done your restore you can fiddle around in your new VM and make sure it all works (and make any adjustments like the Apache site file(s)). If you document any changes you make, then even if you keep working in your old VM then you will know what you need to do when you do your final migration.

Post back if you have issues and I'll try to help you out.

Why?

Reply 2 2016-02-04

Why would you want to do that? Debian backports security patches (i.e. security issues are fixed in the current version) and TurnKey auto installs them every night. That makes the server rock solid stable and secure! :)

It could be done, but unless there is some specific reason there is no value in doing that. Only more work, increased ongoing maintenance overheads and reduced longer term security...

Ah ok...

Reply 3 2016-03-18

Well that's a fairly legitimate reason.

IMO unfortunately there is no good way to install a newer version of Apache. As I've discussed (many times on the forums) once you step away from the version installed from Debian you will need to manually do updates and keep a close eye out for security issues that will need patching. You also lose the "rock solid" stability and may need to tweak things to make them work everytime you update. That is because generally upstream and/or third parties do not usually provide backported security updates. So you actually need to update versions each time you update. That may well bring new features, but will also no doubt from time to time bring regressions or changes that require configuration adjustments.

Personally, if I were you my preferences (from most preferred to least preferred) would run like this:

find an alternative way to achieve your ends that doesn't require a newer version of Apache

install a newer version of Apache from Debian testing (don't forget to pin it properly so you don't accidentally update other packages).

install from upstream or some other alternate 3rd party source