# 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](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

## You need

- An ASP.NET Core project (`dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to `PORT`)
- A PostgreSQL driver reading `DATABASE_URL` at runtime
- An Ample account token with `servers:write`, `databases:read`

## Exact tested configuration

- `build`: `dotnet publish -c Release -o out`
- `runtime`: `dotnet`
- `sizes`: `1vcpu-1gb`
- `start`: `ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll`
- `template`: `dotnet-10`

## 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

- **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.
