The LCB website work should stay aligned with the asdf-managed runtimes that gate our container/image flow. Whenever you touch or document components such as the HTTP cache or webserver, prefer installing and pinning the tool via asdf so the same runtimes are used by every collaborator and the AI operator.
varnish(viahttps://github.com/hyperpolymath/asdf-varnish-plugin.git). This provides Varnish Cachevarnishd/varnishadmbinaries and keeps the HTTP cache on a known version.openlitespeed(viahttps://github.com/hyperpolymath/asdf-openlitespeed-plugin.git). This mirrors the OpenLiteSpeed web server builds we reference in our.ctpmanifests and documentation.
- Install asdf if you don’t already have it (
https://asdf-vm.com). - Add the plugins:
asdf plugin add varnish https://github.com/hyperpolymath/asdf-varnish-plugin.git asdf plugin add openlitespeed https://github.com/hyperpolymath/asdf-openlitespeed-plugin.git
- Install the desired versions and make them globally available (or local per-service as needed):
asdf install varnish latest asdf global varnish latest asdf install openlitespeed latest asdf global openlitespeed latest
- Confirm the installation with
varnish --versionandopenlitespeed --version.
- Whenever you add a new backend, proxy, or runtime, add the corresponding asdf plugin entry (plugin name, repo, version hint) into this file so the handover instructions stay current.
- Update this document before every major change so the AI operator can remind you about installing the latest plugin or pinning a specific release.