If running on a small box, try Alpine, PHP and Lighty are both in their repo.
https://wiki.alpinelinux.org/wiki/Lighttpd
As Alpine only uses like 150 Mb of disk space, you can use the spare 1.5 Gb for other things.
Like some extra slow RAM by creating a NVME / SSD swapfile (swappiness = 100) 
Ah, yes, Alpine seems very nice. Wondered how itâs maintaining/upgrading in the long run?
(Been running Debian and unattended upgrades for a long time. Think I started out with Debian 2.0, or was it 2.1, ran Linux FT, Slackware and RedHat before that.)
Alpine works perfectly, very frequent updates.
And small enough to throw in a Docker container with your lighty/php stack.
That way itâs even easier to control memory usage, the diff in latency is negligible.
As an example :
https://www.cyberciti.biz/faq/how-to-upgrade-alpine-linux-3-4-to-3-5-xx/
# apk update
# apk upgrade --available
# sync
# reboot
Is it safe to put in cron something like this(?):
apk update && apk upgrade --available
I assume version (distro release) upgrades shouldnât skip minor releases? (As in jumping from v3.2 to v3.5 etc.) 
I would be very careful doing this. The minor revisions seem to come out quite often, and unless you check manually, you could miss a step.
I suppose you could parse Index of /alpine/ and decide what to do, but doing a blind âupdateâ will stop working when your subrevision is no longer current and/or there are no security patches for it.
Just keep in mind that itâs not the same as other distributions that tend to autosync subrevisions - which most of them will do. It doesnât attempt to. Thatâs all up to you.
Yes, though havenât tweaked FCGI etc yet. 
Been playing with IPv6 and getting dehydrated to work. (Smoother than certbot + separate Cron job for making the combined cert.)
Will continue to play soon, but first some sleep and work 
