Definitely. Been using it for years for many projects and it’s always the same needs: Let’s encrypt + static files + upstream reverse proxy. I had no idea about keepalive not being default - why isn’t this in all the examples and tutorials?

I'm sure there' space in the tutorial area. A general point for $tech:

If any reader is thinking of writing a tutorial, do check if it's been done before. Likely a grossly simplified example of how to do X while the person reading it has read upteen tutorials on how to do X, Y and Z but still doesn't know where to keep configuration files, or how anything interacts with anything else.

Instead, think of writing Series Of Tutorials That Together Build Moderately Fully Fledged Thing Including Satellite Stuff Like, in this case, Nginx, or SMS, or why XX characters for an email address string, or whatever of the plethora of things to Make It Work are needed.

Some books do this. Not a huge number though, certainly not compared to hit-and-run tutorials.

Call them books. Call them Tutorial Super Series. I don't think the little more time invested would not generate outsized returns.

For that I use linuxserver's SWAG container.

Let's Encrypt automates cert renewal, and SWAG automates having to remember how in the heck to set up LE.