Mark Elvers

I have exactly this issue. I started out with a simple `docker-compose.yaml` to deploy Caddy. This works fine and creates an X86_64 service. ``` version: "3.4" services: live: image: caddy...

Hi @hannesm, these images would have `flambda` or `fp` in the tag. For example, docker pull ocaml/opam:debian-11-ocaml-4.14 docker pull ocaml/opam:debian-11-ocaml-4.14-fp docker pull ocaml/opam:debian-11-ocaml-4.14-flambda docker pull ocaml/opam:debian-11-ocaml-4.14-flambda-fp These are not built...

Hi, Yes, you sure could. Doesn't make much difference in such a short loop but if the code was extended I guess I'd prefer the `while` syntax to get all...

@avsm Yes, I agree. I have renamed it `ocurrent_health_check`, added a ping module and updated http://observer.ocamllabs.io

I have added a machine-readable list of machines:`machines.csv` which is built automatically as part of the GH pages website. The fields a populated from the `_machines/*` YAML files. We can...

@avsm The IPv6 addresses of these two machines appear to have changed. The current values are `2001:bc8:5080:a405::1` (opam-4) and `2001:bc8:1d80:4a00::1` (opam-5). Please can you update the DNS?

@avsm The IPv6 addresses appear to have changed again. opam-4 is now `2001:bc8:5080:a405::1` and opam-5 is now `2001:bc8:1d80:4a00::1`.

@avsm I used https://www.ssllabs.com/ssltest/analyze.html?d=opam.ocaml.org. This was suggested by @hannesm on https://github.com/ocaml/opam/issues/5550#issuecomment-1547326886


@avsm I can also see the wrong address via ``` $ nslookup opam.ocaml.org 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: opam.ocaml.org Address: 151.115.76.159 Name: opam.ocaml.org Address: 51.158.232.133 Name: opam.ocaml.org...