Bitnami wordpress stack stop auto starting update#
There are a few steps to this update which I’ll run through below, but they boil down to something like: It would be nice if all this was possible by taking a snapshot and using it as the basis for a new instance, but sadly that isn’t the case. I read a fair bit about my options, but after looking at the choices I decided the best thing was to do an export and import onto a new Lightsail instance. My version was old and not receiving security updates. Logging into the WordPress admin console a message is displayed which is telling me WordPress would prefer a newer version of PHP please. The LAMP option allows a competent PHP developer to run almost anything on Lightsail.īut after a while running the Lightsail VPS the setup is going to get stale, and because Bitnami bundles everything up, it’s not recommended to go poking around with only a few parts of it. The Bitnami integration allows you to choose from a whole set of Stacks to include upon setup. Click a few buttons and you have a powerful VPS with WordPress up and running for only a few dollars a month. This guidance will walk you though creating a new Lightsail instance with a newer version of PHP installed and moving everything over to it. NB: If you’re hoping for a way to click ‘update php’ or ‘use X version of PHP’ in Lightsail, it doesn’t (at time of writing) exist. Updated 11th May 2021 to confirm that snapshots cannot be used to update the PHP version of a Lightsail Bitnami instance. Updated 25th January 2021 to add an initial paragraph clarifying that you can’t ‘choose’ a PHP version on Lightsail and to further clarify that you must first check which version of PHP a new AWS Lightsail instance will be built with to confirm it will resolve the message being displayed in WordPress. Thanks to Peter and Simon in the comments. Updated 27th September 2020 to consider restart of all services where restarting just apache isn’t enough, and also to share choice when it comes to import first vs SSL first as you may lose s.
0 kommentar(er)
