Ship it

ship-it — go from "works on my machine" to "live on the internet"

When to use this skill

Trigger when the user wants deployment work done. Strong signals:

• "deploy this", "ship it", "put this live"
• "set up Vercel / Railway / Fly / Render"
• "dockerize this", "write a Dockerfile"
• "set up CI/CD for this repo"
• "write the deploy GitHub Action"

Do not trigger for: infrastructure architecture from scratch (use a real infra discussion first), DB provisioning (use schema-architect for schema, then a platform skill for hosting), or for production debugging after a deploy went wrong (read logs, don't redeploy blindly).

The output contract

A deployable artifact that:

1. Has a single, clear deploy command — git push, vercel, flyctl deploy, railway up, whatever the platform's idiom is.
2. Boots in production-like config — secrets via env, no hard-coded localhost, no dev-only middleware in the prod bundle.
3. Has health checks — the platform knows when the app is up.
4. Has logs the team can read — structured JSON, going somewhere they can find them.
5. Documents rollback — one command or one button.

Workflow

1 — Match the app to the platform

Ask 4 questions before recommending:

1. What is it? Static site, Next.js, API + DB, full-stack monolith, background workers, ML inference?
2. Where's the data? Already on managed DB (Supabase, Neon, PlanetScale)? Need one? Local SQLite that needs migrating to managed?
3. What's the budget profile? Generous (AWS, GCP), tight (Railway, Render, Fly, Vercel hobby), zero (Cloudflare/Vercel free tiers)?
4. What's the team's ops capacity? Real DevOps engineer on staff, or solo founder?

Then match:

• Static site / Next.js / Remix / SvelteKit → Vercel (default), Cloudflare Pages, Netlify
• Full-stack monolith with a DB → Railway, Render, Fly.io
• API + workers + cron → Fly.io, Railway, Render
• Containerized anything, multi-region → Fly.io
• Already on AWS / GCP → stay there; use ECS/Cloud Run/Lambda + appropriate manager
• Edge functions, global low-latency → Cloudflare Workers, Vercel Edge

State the choice + 2 reasons in plain prose. Don't bury it in YAML.

2 — Write the platform config

Vercel (vercel.json): only if the defaults don't fit. Most Next.js projects need nothing.

Railway (railway.toml):

[build]
builder = "NIXPACKS"

[deploy]
startCommand = "node dist/server.js"
healthcheckPath = "/health"
healthcheckTimeout = 30
restartPolicyType = "ON_FAILURE"
restartPolicyMaxRetries = 3

Fly.io (fly.toml):

app = "myapp"
primary_region = "ord"

[build]
  dockerfile = "Dockerfile"

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = "stop"
  auto_start_machines = true
  min_machines_running = 1

[[http_service.checks]]
  grace_period = "10s"
  interval = "30s"
  timeout = "5s"
  method = "GET"
  path = "/health"

Render (render.yaml): blueprint-driven; commit the file and the service is reproducible.

3 — Dockerfile when needed

Use a multi-stage build. Production image must be slim and deterministic.

# syntax=docker/dockerfile:1.7
FROM node:20-bookworm-slim AS deps
WORKDIR /app
COPY package.json package-lock.json ./
RUN --mount=type=cache,target=/root/.npm npm ci --omit=dev

FROM node:20-bookworm-slim AS build
WORKDIR /app
COPY package.json package-lock.json ./
RUN --mount=type=cache,target=/root/.npm npm ci
COPY . .
RUN npm run build

FROM node:20-bookworm-slim AS runtime
WORKDIR /app
ENV NODE_ENV=production
RUN addgroup --system --gid 1001 nodejs && adduser --system --uid 1001 nodejs
COPY --from=deps /app/node_modules ./node_modules
COPY --from=build /app/dist ./dist
COPY package.json ./
USER nodejs
EXPOSE 8080
HEALTHCHECK --interval=30s --timeout=5s CMD node -e "fetch('http://localhost:8080/health').then(r=>r.ok?process.exit(0):process.exit(1))"
CMD ["node", "dist/server.js"]

Rules: pin the base image to a major + distro tag (node:20-bookworm-slim), run as non-root, copy only what's needed into the runtime stage, expose one port.

Add a .dockerignore that mirrors .gitignore plus node_modules, .git, *.md, tests/, coverage/.

4 — GitHub Actions CI/CD

Minimum viable for a typical Node app deploying to Fly:

name: deploy
on:
  push:
    branches: [main]
  workflow_dispatch:

concurrency:
  group: deploy-${{ github.ref }}
  cancel-in-progress: false

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npm run lint
      - run: npm test

  deploy:
    needs: test
    runs-on: ubuntu-latest
    permissions:
      contents: read
    steps:
      - uses: actions/checkout@v4
      - uses: superfly/flyctl-actions/setup-flyctl@master
      - run: flyctl deploy --remote-only
        env:
          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}

Rules: never deploy without tests passing. Use concurrency to prevent two deploys racing. Pin action versions to a specific tag (not @main).

5 — Secrets & env

• Never commit .env. .gitignore it.
• Maintain .env.example listing every required variable with a comment about where to get the value.
• For each platform, document the secrets dashboard URL.
• Rotate before launch: any secret that was used in dev or shared in a code review gets rotated before first prod traffic.

6 — First deploy

Walk through together:

1. Provision the project on the platform (CLI: fly launch, railway init, vercel link).
2. Set the secrets via the platform's CLI or dashboard.
3. Deploy: fly deploy / railway up / vercel --prod.
4. Hit the health endpoint and the headline URL. Confirm 200.
5. Tail logs for 60 seconds. Confirm no crash-loop, no spammy error.

7 — Document rollback

Add a DEPLOY.md (or section in README) with:

• Platform + region(s)
• The deploy command
• How to read logs (fly logs, railway logs --follow, etc.)
• The rollback command (fly releases + fly deploy --image <previous>, Vercel "Promote to Production" on prior deployment, etc.)
• Who has access to the dashboard

Patterns and anti-patterns

✅ Do:

• Pin every base image, every action, every CLI version. "Latest" is a time bomb.
• Health check on a path that exercises the app (/health that pings the DB), not just /.
• Use the platform's native secrets store; don't reinvent with KMS unless you actually need it.
• Build once, deploy the same artifact to staging then prod (immutable images).

❌ Don't:

• Don't apt install random tools in a runtime image. The build stage is for that.
• Don't bake secrets into images. Ever.
• Don't deploy on every push to a feature branch. Trigger on main (or after a PR merge).
• Don't set up Kubernetes for a 1-service app. The cost is operational, not just dollar.
• Don't skip the health check thinking "it'll be fine". Without one, the platform routes traffic to a crashing instance.

Example invocation

User: "I have a Next.js app with a Postgres DB. Ship it. Cheap as possible."

1. Recommend: Vercel for the Next.js front, Neon for Postgres (generous free tier, branchable for previews). Reasons: zero-config Next.js deploys; Neon's pooled connections work with Vercel serverless.
2. Wire DATABASE_URL as a Vercel env var (set for Production + Preview, not Development).
3. Add vercel.json only if needed (regions, edge runtime). For most Next.js, defaults are correct.
4. Add .env.example with DATABASE_URL=postgres://....
5. GitHub Actions: run lint + typecheck + tests on PRs; Vercel handles the deploy automatically on merge.
6. First deploy: vercel --prod. Verify health endpoint, log tail for 60s.
7. Document rollback: Vercel dashboard → previous deployment → Promote to Production.

See also

• schema-architect — for the DB migration that must run before/with the first deploy
• security-sentinel — sweep for committed secrets before going live
• git-flow-pro — set up the protected main branch and required checks before connecting CI