Great! And yes, might be there are incoming changes in libavif worth waiting for, and/or libavif / AOM features Squoosh could easily take advantage of for more speed/quality or feature wise.

Since Google bot does not update it's comment with this: CLA has been signed, either click link above and click "Refresh", or the new invocation url.

Minor fixes to package-lock done by NPM, also trigger new build

Noticed there are several newer AOM and libavif releases where out that have focused a lot on compression quality and speed. There is no libavif tag yet using AOM 3.6 so used latests commit here.

Some quick comparison locally:

• Default settings (Quality: 30, Effort: 4): dev (3.1) at 22kb vs update_libavif_aom (3.6) 14.8kb, similar perceived compression artifacts on edges of hearth (305% zoom)
• Higher settings (Quality: 40, Effort: 7): Artifacts goes away on 3.6 build (20.4kb) but not yet on 3.1 build (19kb)
• Speed: 3.6 build seem maybe 5-10% faster on all mentioned quality/effort levels.

Credit: https://unsplash.com/photos/PMxT0XtQ--A

• Default settings (Quality: 30, Effort: 4): dev (3.1) at 425kb vs update_libavif_aom (3.6) 438kb, similar perceived smoothing artifacts on skin (especially when zoomed in)
• Higher settings (Quality: 40, Effort: 7): Smoothing effect goes away on 3.6 build (714kb) but not yet on 3.1 build (644kb)
• Speed: 3.6 build seem maybe 10-20% faster on all mentioned quality/effort levels.

NPM/Yarn: Fixes to be able to build package

Includes:

• PHP ini tweaks for performance and higher default upload limit
• Log rotation to make sure log does not consume gigabytes of disk space
• Asset caching
• Monthly HTTPS cert renewable in cron before it expires
• Redis config tweaks
• smaller tweaks to inline doc

Log rotation is done by tweaking monolog settings, so this will also benefit non p.sh setups (incl local).

Todo on merge up:

• ~For 3.x add PHP preloading config~ (will need to start to use separate build dir for that as server starts before deploy hook runs so as long as this is in a mount it is out of date or missing prior to deploy hook runs and clears cache)

I'm assuming this is no longer relevant ;)

Toggle menus on server status, and let PHP Server icon show if show if server is running or not

This closes #121

This improves usability by giving you a grey icon if server is not running, and a blue icon (the existing one) if server is running. It also changes to trigger openFileInBrowser when clicking icon when server is running so you don't get error about that, but instead get what you expect.

Server not running vs Server running:

Looking for feedback on approach before attempting to improve on test coverage.