The part I am in charge of is documented at https://github.com/ocaml/opam.ocaml.org
I'll check that everything is up-to-date, but it should be > - Anil Madhavapeddy, 23/06/2015 10:43 - > I had to roll back the upgrade due to some issues with Grub2, Xen and > Rackspace Cloud all conspiring to make a Debian Wheezy->Jessie upgrade very > difficult. > > This seems like a good time to look at how to containerise the opam.ocaml.org > services a bit better. Is the existing setup on the VM documented somewhere? > I'd like to take a shot at recreating the VM in a more automated way (and > ensuring that logs are rsync'ed off host). > > This way we can also have multiple VMs serving the HTTP remote over DNS load > balancing if we ever want more redundancy. > > thanks > Anil > > > On 20 Jun 2015, at 01:27, Louis Gesbert <[email protected]> wrote: > > > > No issue that I can think of on my part! > > > > Thanks! > > > >> - Anil Madhavapeddy, 19/06/2015 16:43 - > >> Any objections if I upgrade the opam.ocaml.org VM to Debian Jessie from > >> Wheezy? I've taken a snapshot of the current setup in Rackspace. > >> > >> We need a newer Nginx to support gzip_static, which in turn is needed > >> since we've already hit the 256GB limit for the /builds logs. > >> > >> -anil > >> _______________________________________________ > >> opam-devel mailing list > >> [email protected] > >> http://lists.ocaml.org/listinfo/opam-devel > > _______________________________________________ > > opam-devel mailing list > > [email protected] > > http://lists.ocaml.org/listinfo/opam-devel > >
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
