{"id":3727,"date":"2024-01-07T18:54:31","date_gmt":"2024-01-07T23:54:31","guid":{"rendered":"https:\/\/osric.com\/chris\/accidental-developer\/?p=3727"},"modified":"2024-01-31T14:35:24","modified_gmt":"2024-01-31T19:35:24","slug":"converting-a-wordpress-site-to-a-static-site-using-wget","status":"publish","type":"post","link":"https:\/\/osric.com\/chris\/accidental-developer\/2024\/01\/converting-a-wordpress-site-to-a-static-site-using-wget\/","title":{"rendered":"Converting a WordPress site to a static site using Wget"},"content":{"rendered":"

I recently made a YouTube tutorial on converting a WordPress site to a static HTML site<\/a>. This blog post is a companion to the video.<\/p>\n

First of all, why convert a WordPress site to a static HTML site? There are a number of reasons, but my primary concern is to reduce update fatigue. WordPress software, along with WordPress themes and plugins, have frequent security updates. Many sites have stable content after an initial editing phase, the need to apply never-ending security updates for a site that doesn’t change doesn’t make sense.<\/p>\n

The example site I used in the tutorial is www.stress2012.com<\/a>, a site for an academic conference\/workshop that was held in 2012. It’s 2024: the site content is not going to change.<\/p>\n

To mirror the site, I used Wget<\/a> with the following command:<\/p>\n

<\/p>\n

wget -k -r http:\/\/www.stress2012.com<\/code><\/pre>\n
That created a www.stress2012.com directory in my current working directory. That directory contained all of the HTML files Wget found on the site, as well as all the non-HTML assets (images, stylesheets, Javascript files, etc.).<\/p>\n
The document root for the WordPress site was set up at \/var\/www\/stress2012<\/code>. I copied the site mirror to an adjacent location:<\/p>\n
sudo cp -r www.stress2012.com \/var\/www\/www.stress2012.com<\/code><\/pre>\n
The permissions were off after copying using sudo privileges, so I updated those:<\/p>\n
sudo chown -R chris:www-data \/var\/www\/www.stress2012.com<\/code><\/pre>\n
Then I copied the Apache web server config file for the WordPress site, \/etc\/apache2\/sites-available\/stress2012<\/code>, to an adjacent location:<\/p>\n
sudo cp \/etc\/apache2\/sites-available\/stress2012 \/etc\/apache2\/sites-available\/stress2012-static<\/code><\/pre>\n
The most critical change in that file was to update the document root to \/var\/www\/www.stress2012.com<\/code>.<\/p>\n
After that change was made, I disabled the WordPress site, enabled the static site, and reloaded the Apache web server:<\/p>\n
sudo a2dissite stress2012.conf\r\nsudo a2ensite stress2012-static.conf\r\nsudo systemctl reload apache2<\/code><\/pre>\n
That’s it! The WordPress site has now been converted to a static site.<\/p>\n
The WordPress site included a search form, which relied on PHP and MySQL. The HTML is faithfully reproduced on the static site, but of course it is not functional. I examined the search form and found that the first line of the form contained the presumably unique string “searchform” followed by 4 additional lines.<\/p>\n
I removed the search form from all the HTML pages on the static site using the following command:<\/p>\n
cd \/var\/www\/www.stress2012.com\r\nfind -name *.html -exec sed -i '\/searchform\/,+4d' '{}' \\;<\/code><\/pre>\n
That latter command is not something you’d want to run on a production web site unless you’re feeling really, really<\/em> confident. In this case, I knew I could revert to the WordPress site if anything went awry.<\/p>\n
That’s one of the great things about this particular method of converting a WordPress site to a static site: it’s easy to re-enable the WordPress site and disable the static HTML site if needed.<\/p>\n
Other reasons you might want to use a static HTML site aside from avoiding update fatigue?<\/p>\n