> You are welcome to the setup here - it's already allocated - though I do
> request that you wait a few weeks, as a new server should be arriving,
> and the current one will be repurposed just for scheme-community
> projects. Until that point, I'd rather not complicate the setup. :)

Great - no rush.

Meanwhile, I'm having trouble pushing many big files to a GitHub repo.
Their servers are configured to receive no more than 2 GiB per `git
push`. Git is overzealous about bundling individual files added to a
repo into huge "pack files" internally, and it insists on sending these
huge packs into GitHub as is, so GH's limit is constantly blown. And GH
may tighten the hard limit on repo size in the future.

I looked briefly into Git LFS (Large File Storage) - an extension
jointly developed by GitHub and GitLab among others. But GH and GL have
tight limits on LFS size too. It's easy to buy more room for $5/month,
but for that price you can rent a Linux VPS with more storage.

Googling briefly about S3 buckets, Amazon doesn't recommend publishing
their contents directly (it should work, but there's a warning in the
control panel). I don't know which AWS service they officially suggest
for static hosting.

VPS hosts now tend to sell "block storage" add-ons. Our initial server
is at Vultr.com, which sells 10 GB for $1/month. This seems like a good
(cheap and easy enough) way to get more space.

(Next to "block storage", another term of art is "object storage". I
assume the latter means S3 workalikes.)