-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
inbox.ocaml.org VM #15
Comments
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:
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. |
Point to the mirror of the caml-list archive provided by Leah Neukirchen at https://inbox.vuxu.org/caml-list/ as https://inbox.ocaml.org/caml-list/ is down. See: * #550 * ocaml/infrastructure#15
Point to the mirror of the caml-list archive provided by Leah Neukirchen at https://inbox.vuxu.org/caml-list/ as https://inbox.ocaml.org/caml-list/ is down. See: * #550 * ocaml/infrastructure#15 Co-authored-by: Cuihtlauac ALVARADO <cuihtmlauac@tarides.com>
This came up again on ocaml/ocaml#12420 -- just bumping this for @mtelvers and @tmattio to consider as part of the ocaml.org website work. |
So is this ever coming back or not? |
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 😅 I was wondering if there is interest in running an official version again. |
Yes, definitely. I'll try to moving this along this week. |
I have made some progress. https://inbox.ci.dev/caml-list/ |
@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.
The text was updated successfully, but these errors were encountered: