![]() ![]() Redis is not mandatory, but since I had been using it, I decided to re-install and configure it.Please read the full post to understand the procedure.It is possible that you may not get the same results, so please back up all your data and have a rollback plan.For a short period of time, my site showed no content and if this is not acceptable, then this procedure is not suitable for your migration.This procedure resulted in a small downtime which may vary based on your sites content. These steps worked for me when I migrated my site.Reset the upload limits on the new AWS Lightsail instance.Import data previously exported WordPress data to new instance.Setup Let’s Encrpt SSL certificate on the new instance.Change the DNS record for your blog to point to the new AWS Lightsail instance.Change upload limits on the new AWS Lightsail instance.Create a new Bitnami WordPress stack on AWS Lightsail.Take a Snapshot of your AWS Lightsail instance.Create an export of all WordPress data from existing instance.There was a short amount of downtime involved with my procedure, but after having two failed migrations, I knew I had to do things differently. Here is an overview of the steps I took to complete the entire process. So, I had make a few changes to the upgrade process to complete and I am going to highlight those in this post. I followed the steps but in my case, I kept running into an issue with links being generated incorrectly by WordPress. Please do read the post as it lists detailed steps on the upgrade steps. I kept putting off the upgrade, until I came across this post giving some clear answers to how a successful upgrade was done. ![]() The instance would be based off a new OS image and fully patched as of it’s release date. I knew the best solution would be to move to a completely new AWS Lightsail instance. I searched the Bitnami documentation and other sites on the internet, but none of the presented options seemed clear or viable. The challenge was to find a way to upgrade the stack. The version of PHP on the server was old and insecure. ![]() It could be due to a new feature being released, bug fix or update to fix security issues discovered.įew months ago, I noticed that when I logged into the WordPress admin console, there was a warning to upgrade the PHP version on the server. ProblemĪll software at some point of time will end up requiring update. The core software is version locked and cannot be upgraded easily.īitnami does provide upgrade instructions but they seem to describe the overall process more, than actually provide detailed step to carry out the task. However, the Bitnami stack is bundled in such a manner that it becomes difficult to upgrade software. With a clicks and configuration it is fairly easy to launch a new site. The instance contains core software that you need to run a WordPress site. The instance is based off a Bitnami WordPress stack. This WordPress blog is running on an AWS Lightsail instance. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |