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
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis supplied.
You need
- An ASP.NET Core project (
dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT) - A PostgreSQL driver reading
DATABASE_URLat runtime - An Ample account token with
servers:write,databases:read
Exact tested configuration
build:dotnet publish -c Release -o outruntime:dotnetsizes:1vcpu-1gbstart:ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dlltemplate:dotnet-10
Steps
Build and start.
dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT; the server must bind0.0.0.0onPORT.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"Verify. Fetch the live URL and
/p/migratedon 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
- November 6, 2026 · canary run
ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).
Tested examples
- ASP.NET Core pattern fixture. Verified schema changes on ASP.NET Core.
What it doesn’t cover
- Verified on the dotnet-10 template at
s-1vcpu-1gb. - Managed PostgreSQL 16 with pgvector.