lokl-cli VS wp2static

It might be worth mentioning that Lokl [0] seems to be from the same author [1] as the "wp2static" plugin [2], my and many others go to for static site generation of WordPress.

I find Lokl and interesting take, although the usual self-serve script is kind of annoying for power users (what I mean is that this bash scripts tried to do everything for you and it's less transparent), I recommend the repo [4] as the source of the actual Dockerfiles, that you could just reference in something like a docker-compose setup.

The Dockerfiles are kind of surprising since they read more like a an ansible-playbook than like a Dockerfile. This one image has it all - php, nginx, mariadb, phpmyadmin and who knows what else [4]. It's an interesting approach to Docker images, certainly against the recommendation but might have some good reasoning for something as special as WordPress.

[0]: https://github.com/leonstafford/lokl-cli

[1]: https://github.com/leonstafford

[2]: https://github.com/leonstafford/wp2static

[3]: https://github.com/leonstafford/lokl

[4]: https://github.com/leonstafford/lokl/blob/master/php8/Docker...

But, in the last builds, I added support to run Lokl noninteractively, by setting environment variables. Ugh, Readme on Lokl main GitHub repo now stale, but lokl-cli's source shows how to run it as such: https://github.com/leonstafford/lokl-cli/blob/master/cli.sh

Download and Install WP2Static Plugin

> It is not actually that hard to run Wordpress securely. Stick to supported plugins and themes, and install security patches quickly when they are released.

Depending on your site's functionality, it may also be possible to run a static WP site:

* https://wordpress.org/plugins/simply-static/

* https://wp2static.com

You do all your regular updates via the CMS, but, instead of putting the dynamic site on the public Internet, you generate static files and point your public web server's HTML rootdir at those.

Also, for a bit more complex although richer in features workflow, you might try Wordpress with the Block Editor (or any page builder like Elementor) and the [WP2Static](https://github.com/WP2Static/wp2static) plugin, which allows you to turn a Wordpress site into a static one!

The closest "free" option I can think of is Oracle Cloud, but /r/oraclecloud shows plenty of horror stories in registration and maintaining an instance. If you don't actually need interactive features, WP2Static on your local instance to be deployed to Cloudflare Pages might work.

> Most WP sites should be static sites.

https://wordpress.org/plugins/simply-static/

https://wp2static.com

Depending on the site, ask yourself "How dynamic does it actually have to be?". Perhaps using the GUI to update the content, and then creating static files and serving those may be an option:

* https://wp2static.com

You could also use WordPress as a SSG with the WP2Static plugin — https://github.com/WP2Static/wp2static/

What is wrong with using Wordpress? I believe now one can get Wordpress to have 'static site' capabilities these days [0]

[0] https://wp2static.com/