You are here
bhruska - Fri, 2022/03/18 - 18:24
What's the status of 17.0? Looking to have the latest PHP, etc for a new site. Your email said it was "getting close" in January... LOL.
Thanks,
Brian
Forum:
Tags:
What's the status of 17.0? Looking to have the latest PHP, etc for a new site. Your email said it was "getting close" in January... LOL.
Thanks,
Brian
Just got a lot more important
Discovered a crash in my new site that's because of PHP not being current. I suppose if 17.0 is a ways off I can figure out how to upgrade PHP. Any directions on how to do that? Just concerned I'd screw it up. Would be better to have a nice shiny new VM from you guys!
Thanks,
Brian
Yeah unfortunately, my crystal ball was a little cloudy! :)
One of the significant downsides of "release when ready" release schedule is there is almost no reliable way to predict when the release will actually be ready! :)
So yeah, it was "getting close" in January. But the "few little pieces" left, ended up being a fair bit bigger than anticipated. And then we hit a few other issues... Then war started in Ukraine, which put more spanners in our works (we have a couple of Ukrainian devs who help out with releases - who are obviously no longer available) and pushed things back further.
Anyway, I'm still hoping that it will be really soon, but I'm loathe to say too much more, now that I've been proved wrong so many times before...
As for PHP, v17.0 will only have PHP7.4, so if you want "current" PHP (latest is 8.1) you'll likely want to install from sury.org repo regardless. I have a half-finished tool to make is super easy to change PHP version on TurnKey, but it's still work in progress and I have no idea when I might have some spare cycles to complete it.
In the meantime, please see this post on how to upgrade PHP that I did late last year.
PHP Update
Sorry to hear about your Ukraine issues. Its a messed up world right now for sure.
Not sure why you'd want to ultimately release a new core without the latest PHP. Obviously there's more to this than I understand, but I don't get it when you are going through all the effort to do a new release... no matter when its done.
Anyhow, I understand your challenges, and wish you the best.
If I go through the suggested steps to upgrade PHP myself, will the automatic security updates still be handled without further changes?
Thanks for all your help.
Brian
Thanks,
Brian
Any progress on 17.0?
Just wondering if you are still progressing on this update, or if its a dead issue.
Thanks,
Brian
Thanks,
Brian
It's v17.1 now...
Hi Brian. There has been lots of progress, but unfortunately, not all of it has been in the right direction... So we're working on v17.1 now... For more details, please see the blog posts tagged with '17.x'.
IIRC WordPress was what you are after right? I'll try to get that into the next batch. Although as noted in the blog posts, I'm not sure when we'll have OVAs.
Wordpress 17.1
Any progress on 17.0?
Its been a while since I checked. Any progress on this issue?
Thanks,
Brian
Thanks,
Brian
Thanks for your patience and deep apologies for the delays...
You are right, it's been a while, but unfortunately, it's still not done yet. My deepest apologies on that. It's pretty embarrassing really, as our current WordPress app (which is incidentally one of our most popular) is getting very dated now and seriously needs an update. I suspect that it may have even turned a few new potential TurnKey users off using TurnKey. :(
To provide some context, the hold up is a combo of a good idea gone wrong and a whole raft of "behind the scenes" dramas and issues that have sidetracked me (mostly infrastructure, but other bits and pieces too).
The good idea gone wrong was to follow your (and others') hints and develop a super simple way to use newer PHP - built in from the get go. The broad idea is still sound, but the approach I initially took wasn't thought through enough and ended in a dead end. I could have persevered, but the flaw in my design would have made it harder for us to maintain in the long run. I have the seed of a much better approach, but haven't had the time to start prototyping it yet.
And that was before we had the raft of other issues that popped up (including the website being broken for days while I scrambled to work out the problem and migrate to a new server); seemingly one after another...
Anyway, I don't want to harp on about it and I certainly don't want you to think that I'm trying to make excuses. It's definitely a failure on my behalf and my deepest apologies on the ridiculous delay on this.
Regardless, hopefully you'll be glad to hear that the WordPress updated release is currently in progress! I don't have a firm ETA, but I would expect it to definitely be completed within the next month, fingers crossed, within the next couple of weeks. I'll try to remember to post back here as soon as it's available (i.e. once the image is on our mirror - even if that's before it's officially published).
Update Progress
Lamp Question
Hello Jeremy,
I have a silly question about this:
Isn't Lamp basically the same as wordpress ( except extra wordpress to pull and unzip ) ?
I could just install wordpress and I didn't notice any difference ?
I only ask because Lamp is on 17.1.1 and I wanted to re-install.
Greetings
Yes our WordPress appliance is based on our LAMP app
Yes our WordPress appliance is based on our LAMP appliance, so if you were to install WordPress on top of LAMP then it would more-or-less get you the same outcome. Off the top of my head, beyond initial config and secret regeneration (which isn't really required if you install from scratch yourself) the only thing you'd be missing is wp-cli (WordPress admin cli tool). But if you don't use that then you won't miss it. If you want to try it out, there's no reason why you couldn't install it yourself if you wanted.
Thanks for your quick answer
Thanks for your quick answer
Then I can leave everything as it is.
But I have decided to port the website to a WordPress plugin.
(I'm not going to advertise this ;-)
All other ways that were mentioned to me led to ssl errors that I simply could not get rid of.
TBH I'm not completely sure what you're referring to...
TBH I'm not completely sure what you're referring to...
Having said that, I'm not super familiar with WordPress itself, nor PHP in general. But (as you probably could guess) I'm fairly intimately knowledgeable about Debian in general and TurnKey in particular. So if you hit issues on TurnKey, please feel free to share (ideally in a new thread) and I'll do my best to advise.
Good luck! :)
Add new comment