docs: add Node.js deploy guide and runnable example for Datum compute#132
Open
scotwells wants to merge 2 commits into
Open
docs: add Node.js deploy guide and runnable example for Datum compute#132scotwells wants to merge 2 commits into
scotwells wants to merge 2 commits into
Conversation
scotwells
force-pushed
the
docs/deploy-guide-node
branch
from
a24bf18 to
e767314
Compare
scotwells
changed the title
scotwells
force-pushed
the
docs/deploy-guide-node
branch
from
e767314 to
436198a
Compare
scotwells
force-pushed
the
docs/deploy-guide-node
branch
from
436198a to
10a329f
Compare
ecv
previously approved these changes
Jun 3, 2026
savme
previously approved these changes
Jun 4, 2026
…guidance Verified corrections from deploying a real Node app: - rootfs must be CPIO, not erofs: an erofs initrd does not boot on base-compat:latest ((i0 EXP) at 0.00ms, no logs). Drop rootfs.format and pass --rootfs-type cpio. - pin the build stage to linux/amd64: base-compat is x86_64 and the rootfs copies x86_64 musl libs, so arm64 hosts must cross-build. - document the ~150 MiB initrd boot ceiling and rootfs slimming (bundle to a single file, drop node_modules/dev deps); -M does not affect it. - add a framework/SSR section (run npm run build, ship built output, watch for build tools absent from node:22-alpine). - add an env vars & secrets section: inject via env secretKeyRef to an existing default-namespace Secret; file mounts need erofs (does not boot), so prefer env-from-secret on the CPIO runtime. - note registry publish-vs-pull and the RAM-backed/ephemeral rootfs; reframe -M as a build hint. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this delivers
A self-contained guide that takes a developer from a Node.js HTTP service in source form to a live, reachable Instance on Datum compute, plus a runnable example they can deploy as-is. It lowers the barrier to a first successful Node.js deploy: package the app as a Unikraft unikernel on the
base-compatruntime, publish to the metro registry, deploy withdatumctl compute deploy, and verify the HTTP response end to end.Changes
docs/guides/deploy-a-node-app.md(moved out ofdocs/compute/guides/).examples/hello-node/materializes every file the guide inlines, so a reader can clone and ship without copy-pasting:app.js— the Node HTTP service (responds on/and/healthz)package.jsonDockerfile— builds the minimalscratchrootfs with thenodeinterpreter and its shared librariesKraftfile—base-compat:latestruntime packagingworkload.yaml— the DatumWorkloadmanifestREADME.md— one-line summary, link back to the guide, and the key build + deploy commandsThe guide gains a single pointer line directing readers to the example folder.
🤖 Generated with Claude Code