ocaml
inbox.ocaml.org VM
@nojb has got everything ready (as a Dockerfile) for a inbox.ocaml.org replacement, but it needs provisioning as a Scaleway VM. Depends on having #14 for backups first, so history doesn't repeat itself.
Backups are now online, so we can now look at getting Inbox back. I'm trying hard to minimise the energy footprint of the ocaml.org infrastructure, so I'm wondering if we can do one better than having a VM dedicated to inbox.ocaml.org.
@mtelvers, might you have time to look into whether:
- we can maintain a Git version of the caml-list mbox, via some mail listening service (ideally, that we don't have to host ourselves). @nojb has one here: https://github.com/nojb/caml-list-mirror
- then, can we do a static rebuild of inbox.ocaml.org using public-inbox, and just serve the HTML, instead of having a perl service running.
- this could all be coordinated rebuilds via deploy.ocaml.org, rather than bespoke cron scripts.
- if this works, then we can also do the same with the lists.ocaml.org mbox archives and combine those into one mailing list service.
- bonus points if the resulting HTML can be styled to be compatible with the ocaml.org design in the future, so we can integrate it properly :-)
If this is all too much trouble, and we need to just get inbox.ocaml.org back in its former form, then we can do that too, but it would be nice to look into whether we can minimise our ongoing energy costs.
This came up again on https://github.com/ocaml/ocaml/pull/12420 -- just bumping this for @mtelvers and @tmattio to consider as part of the ocaml.org website work.
Linking in this Discuss note from @nojb, it was being mirrored at https://inbox.vuxu.org/caml-list/, so the archive is at least still available online up to 2022.
Yes, I host that archive :sweat_smile: I was wondering if there is interest in running an official version again.
