ocaml-dune / ocaml-dune/binary-distribution
Upload `metadata.json` to deployment server and use it from there
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Having the metadata.json on the server would allow the install script to download the metadata and then figure out which tarball to download from there.
That would save us having to run a sandworm instance that does the same thing but in OCaml and make it easier to scale and test as all the data is static. There is no Docker instance to start and restart and rebuild which should reduce the number of moving parts and things to worry about.
That way the project would shrink to just building the static assets and uploading them, from where a static web server can serve them (and they can be cached by a CDN).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the install script, metadata.json generation and upload path, and the sandworm deployment configuration. Trace how the install script currently discovers tarballs, then define the static-server flow so metadata.json and assets are uploaded together and sandworm is no longer required; verify the install path against the published static assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ocaml, shell
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100