[yuravk]

Why

Since #379, the almalinux/* Vagrant boxes are published in our own catalog on S3, which is now served at https://vagrant.almalinux.org (CloudFront in front of the bucket's vagrant/ folder). With HCP Vagrant gone (shutdown on 2026-12-31), users lose the Discover page that listed the boxes, their versions and providers. Also, the repository still named the bucket's S3 address as the one to use.

What changes

The catalog page (tools/vagrant-catalog-index.html)

A page at the catalog's address showing what the HCP Vagrant Discover page did:

• the setup snippet, VAGRANT_SERVER_URL=https://vagrant.almalinux.org, for Linux/macOS, PowerShell and cmd;
• the catalog boxes (almalinux/8, 9, 10, 10-x86_64_v2, 10-kitten, 10-kitten-x86_64_v2), with their providers, architectures, latest version, release date and number of versions, filterable by text and provider;
• per box: how to use it (Vagrantfile, vagrant init, vagrant box add) and its versions, newest first. Each version lists every provider and architecture with the box size, sha256 (copyable) and download link, filterable by provider and architecture.

How it works:

• One static file in the almalinux.org style: Montserrat, its navy and accent colours, with the logo and favicon inline. No build step, no external scripts.
• Reads the catalog live from <root>/almalinux/<box>.json (same origin) when it loads. That's the root on vagrant.almalinux.org and /vagrant on the bucket's own address. Publishing needs no change to the page. The bucket can't be listed publicly, so BOXES names the catalog boxes, and a new catalog box needs adding there.
• Old HCP versions without an architecture (unknown; all x86_64 boxes of almalinux/8 and almalinux/9) show the architecture of their box file. The catalog itself keeps unknown, which Vagrant accepts on any host.
• Box sizes come from HEAD requests to the box files. The bucket's CORS rule allows GET/HEAD from https://vagrant.almalinux.org (already applied).

The page is uploaded by hand when it changes: as the vagrant/ object (the root of vagrant.almalinux.org), vagrant/index.html and vagrant. The command is in VAGRANT_BUILD_TEST_PUBLISH.md, "The catalog page".

vagrant.almalinux.org as the catalog's address

• vagrant-build-test-publish.yml: a new VAGRANT_SERVER_URL: https://vagrant.almalinux.org env. The publish job's summary and Mattermost message now name it.
• Reads and checks stay on the bucket. The job still reads the current catalog from the bucket's own address and checks its upload there, because CloudFront may serve a file up to its max-age (5 minutes) old. Reading through the CDN could build on a stale catalog.
• Docs: VAGRANT_BUILD_TEST_PUBLISH.md describes vagrant.almalinux.org as the address users set, with the bucket address as the origin.