www.ocaml.org needs to migrate machine host

[avsm]

See ocaml/ocaml.org#1169 for the overall tracking issue.

The existing www.ocaml.org needs to migrate host fairly urgently, so this is a good time to take stock of its deployment mechanism.

• currently: cron job on the VM rebuilding it. Not currently working due to an issue compiling ssl since the Use cohttp as HTTP client for planet and CWN #1151 change ent in. Hence merged PRs aren't showing up.
• next step: to unblock the content not showing up, the Dockerfile does work fine, so I'm going to fix that up for a deployment change to a new VM. This will mean that there will be a blip in the self-hosted hits tracking -- I'll need to talk to @Chris00 to get more information on how that works.
• after stability is back: break up the website such that external data (such as rss feeds or opam packages) can be committed to separate git repos, so that the main website build is just a series of submodules. This should be fairly easy to automate using ocurrent, and developer experience should be the same (just need to add git clone --recursive to get the submodules.

[avsm]

New hosts set up, and adding a deployment to ocurrent/ocurrent-deployer#40 (live at https://deploy.ocamllabs.io). This is the ocurrent-based deployer that will be used for the nextgen opam CI, so it's convenient for everything to be managed from one place.

[avsm]

http://www2.ocaml.org is now working reliably -- just needs TLS/LE setup to activate HTTPS and then can migrate to www.ocaml.org

[pw374]

any update on this? :)