forked from
anil.recoil.org/monopam-myspace
My aggregated monorepo of OCaml code, automaintained
deploy.sh: add day10 batch as production alternative in setup instructions
Explain the relationship between `jtw opam` (local-dev path used by
the script) and `day10 batch --with-jtw` (production path that handles
switch creation, dependency solving, and universe assembly in containers).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
+23
+23
odoc-interactive-extension/deploy.sh
+23
odoc-interactive-extension/deploy.sh
···
6
6
#
7
7
# ─── One-time setup ──────────────────────────────────────────────────────
8
8
#
9
+
# This script uses `jtw opam` to build universes from local opam switches.
10
+
# In production, `day10 batch --with-jtw` does this at scale inside
11
+
# containers (see docs/jtw-admin-guide.md). The manual switch setup
12
+
# below is the local-dev path for running these demos.
13
+
#
9
14
# 1. Create the opam switches. The "default" switch is used for building
10
15
# the monorepo and for the yojson 3.x universes.
11
16
#
···
40
45
# dune build @install && dune install
41
46
#
42
47
# After this, `jtw opam --help` should work.
48
+
#
49
+
# ─── Production alternative (day10) ─────────────────────────────────────
50
+
#
51
+
# For building universes at scale (e.g. all of opam), use day10 instead
52
+
# of manual switches. day10 runs builds in OCI containers with cached
53
+
# overlay layers. See day10/docs/ADMIN_GUIDE.md for full details.
54
+
#
55
+
# dune exec -- day10 batch \
56
+
# --cache-dir /var/cache/day10 \
57
+
# --opam-repository /var/cache/opam-repository \
58
+
# --with-jtw \
59
+
# --jtw-output /var/www/jtw \
60
+
# --html-output /var/www/docs \
61
+
# --with-doc \
62
+
# @packages.json
63
+
#
64
+
# day10 handles switch creation, dependency solving, js_top_worker
65
+
# installation, and per-package universe assembly automatically.
43
66
#
44
67
# ─── Usage ───────────────────────────────────────────────────────────────
45
68
#