Apply database schema changes for Gin · Ample Computer

Apply database schema changes for Gin

Schema changes for a Gin app on Ample. Verified on Gin: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build).

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build); the server must bind 0.0.0.0 on PORT.

  2. Run migrations as the release command. Ample runs the command before activation and fails the release if it exits non-zero; keep migrations idempotent.

    $ ample deploy . --name <app-name> --public --release-command "./app migrate"
    
  3. Verify. Fetch the live URL and /p/migrated on the example; on failure read the build and runtime logs.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL · http get / → “ample canary gin patterns”
✓ migrated check from the example · http get /p/migrated → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run
    Gin pattern fixture deployed on Ample (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build)); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).

Tested examples

What it doesn’t cover