meteor-deploymentlisted
Install: claude install-skill meteor/agent-skills
# Meteor deployment
`meteor build` produces a self-contained Node bundle that runs anywhere
the matching Node.js version runs. Galaxy is the first-party host;
Docker / Kubernetes / SSH-to-a-Node-host all work too.
For Android/iOS artifacts and native HCP compatibility, use `meteor-native`.
Check actual native configuration as well as compatibility hashes: permission
or other native configuration changes can require a new binary with an
unchanged hash.
Match the Node version to the bundled Meteor Node:
| Meteor | Node major |
|---|---|
| 3.0 | 20 |
| 3.1 through 3.4 | 22 |
| 3.5+ | 24 |
Mismatch causes runtime errors. Run `meteor node -v` to confirm.
## Decision flow
1. Galaxy? Choose Git Push to Deploy or the Meteor CLI. Configure Galaxy's
settings source, build hooks, health checks, and domains from
`references/galaxy.md`.
2. Docker / Kubernetes? `meteor build --directory ./build --server-only`
skips platform-specific mobile artifacts. Use
`--architecture os.linux.x86_64` for a cross-build.
3. SSH to a Node host? Same `meteor build`, scp the bundle, install prod
deps under `bundle/programs/server`, run `node main.js`.
4. Vercel / Netlify / serverless? Not supported. Meteor needs a
long-lived Node process with a WebSocket.
## Required environment
| Var | Purpose |
|-------------------|--------------------------------------------------------------|
| `ROOT_URL` | Absolute exter