nginx-pagespeed VS swizzin

I’m unreasonably proud of setting up automated patching for NGINX to include PageSpeed: https://github.com/knyzorg/nginx-pagespeed

The whole project is basically just a ‘sed’ command, but piecing everything together (where to get the source code, how to build nginx, make Debian packages, publish packages, etc) was a major effort.

I found myself in the valley between people who didn’t know and had no means of learning, and those who knew and for whom it was obvious. I’ve learned a lot.

Shameless plug: https://www.bbss.dev/posts/pagespeed/

GitHub repository with sources here: https://github.com/knyzorg/nginx-pagespeed

I recently returned to those notes to entirely automate the process using GitHub Actions. The work is open-source and available on GitHub.

Surprisingly few people seem to have heard of modpagespeed which I think can be attributed to an absence of packages coupled with the difficulty of installation.

I knew I had to build something like this the day GitHub actions came out, but haven't gotten around to it until the holidays!

While this HN thread is quite old now, it still provides some context on what it's all about: https://news.ycombinator.com/item?id=11018861

GitHub repository with sources here: https://github.com/knyzorg/nginx-pagespeed

Why not just use Swizzin? https://github.com/swizzin/swizzin

Yes. I suggest using a seedbox install script like Swizzin which makes the whole process very simple. All you have to do is make sure the proper ports are opened both on the instance itself and in the ingress rules for the security list in the VCN.

Swizzin, Cloudbox or /r/plexshares are the easiest ways.

Biggest established tooling projects are Cloudbox (Docker), and Swizzin' (not Docker).

See also Cloudbox, and Swizzin'. The latter is a more complete, alibeit not Dockery, soln.

Big player in this space is Swizzin, should you have not seen it.