Skip to content
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

Open
avsm opened this issue Nov 4, 2022 · 7 comments
Open

inbox.ocaml.org VM #15

avsm opened this issue Nov 4, 2022 · 7 comments
Assignees

Comments

@avsm
Copy link
Member

avsm commented Nov 4, 2022

@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.

@avsm avsm self-assigned this Nov 4, 2022
@avsm
Copy link
Member Author

avsm commented Dec 15, 2022

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 de# 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.

@avsm avsm assigned mtelvers and unassigned avsm Dec 15, 2022
cuihtlauac pushed a commit to ocaml/ocaml.org that referenced this issue Dec 16, 2022
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
cuihtlauac added a commit to ocaml/ocaml.org that referenced this issue Dec 16, 2022
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>
@avsm
Copy link
Member Author

avsm commented Jul 24, 2023

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.

@leahneukirchen
Copy link

So is this ever coming back or not?

@dra27
Copy link
Member

dra27 commented Mar 10, 2024

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.

@leahneukirchen
Copy link

Yes, I host that archive 😅 I was wondering if there is interest in running an official version again.

@mtelvers
Copy link
Collaborator

Yes, definitely. I'll try to moving this along this week.

@mtelvers
Copy link
Collaborator

I have made some progress. https://inbox.ci.dev/caml-list/

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants