undefined | Better HN

0 pointstzs1y ago0 comments

Suppose I want to have a Wordpress site, and am considering the following options.

1. I create an Amazon Lightsail server set up using the Wordpress image as described here [1].

2. I get a virtual server somewhere, install Debian, do "apt install wordpress curl apache2 mariadb-server", and configure things as described here [2].

3. I get a shared hosting account at some place that includes cPanel or something similar, and install Wordpress through that.

4. I get a server, maybe virtual or maybe physical, install a Linux distribution, and install Wordpress by downloading the zip file from https://wordpress.org/download/ and following the install instructions linked that page.

5. I get an account at WP Engine and use their hosting service.

How much variation is there between these different ways I might set up a Wordpress site when it comes to how much load my site places on the Wordpress autoupdates infrastructure?

[1] https://aws.amazon.com/getting-started/hands-on/launch-a-wor...

[2] https://wiki.debian.org/WordPress

0 comments

chuckadams1y ago

They're all going to hit wordpress.org for plugins and themes. I would definitely stay away from Debian's packages, which are outdated the moment they're installed, and the setup looks painfully fiddly and manual anyway.

An alternative to wp.org's infrastructure would be the likes of https://roots.io/bedrock, which uses composer to install and update plugins and themes along with wordpress itself. The infrastructure it uses is called WordPress Packagist, which is run by outlandish.com using github as the distribution infrastructure. The whole thing is open source, so you could run your own wpackagist service if you like.

Using bedrock in a container, I upgrade the site by building and uploading a new container image. Anything goes wrong, I roll back to the previous image. Cattle, not pets.

j / k navigate · click thread line to collapse