Keywords: WordPress Multisite - AWS - How to - Other
I'm helping out a non-profit move their web-site from the paid proprietary solution to the Bitnami Multisite Wordpress AMI.
Two issues I need help with:
- Initial multisite config:
After spinning the Bitnami VM, the configs had references to the Amazon IP addresses in both the wp-config.php and the database, so I've done:
sed -i 's/220.127.116.11.xip.io/wordpress.npo.org/g' /opt/bitnami/apps/wordpress/htdocs/wp-config.php
wp search-replace '18.104.22.168.xip.io' 'wordpress.npo.org' --skip-columns=guid
Things worked well, however on each reboot, I believe the wp-config.php entry changes. Also, when I follow the Bitnami guide on backing up and restoring everything in the new VM, the wp-config.php still has an entry for the new IP address.
How can I permanently convert everything (including the new VMs) to use the wordpress.npo.org rather than the IP-based domain name instead? Especially during upgrade to the newer AMI, I'd like to keep the elastic IP assigned to the old VM until everything is set up.
- Moving production to Wordpress
I initially configured Wordpress install to work on wordpress.npo.org. Now that the web-site has been built up, we're ready to move. What's the proper way of changing the primary Wordpress install to just npo.org? I will edit the hosts file on the local machine to test before actually switching DNS records, my question has to do with the Wordpress config.
Also, if I reconfigure the main site to be npo.org, would the www.npo.org work automatically with the proper DNS record set up or would I need to mess with the domain mapping or some such?
Finally, a request -- could you please include the certbot in the Wordpress multisite AMI? That way I could just request a new certificate from letsencrypt upon upgrade to the newer AMI without having to install anything.