Apply database schema changes for ASP.NET Core · Ample Computer

Apply database schema changes for ASP.NET Core

Schema changes for a ASP.NET Core app on Ample. Verified on ASP.NET Core: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT; 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 "python3 migrate.py"
    
  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 asp net core patterns”
✓ migrated check from the example · http get/p/migrated → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); 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