Connect Postgres for ASP.NET Core · Ample Computer
Connect Postgres for ASP.NET Core
Database connection for a ASP.NET Core app on Ample. Verified on ASP.NET Core: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok). Build and start: dotnet publish -c Release -o out in the builder, then dotnet
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 no DATABASE_URL is supplied.
You need
- An ASP.NET Core project (dotnet publish -c Release -o out in the builder, then dotnet
.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
- Build and start. dotnet publish -c Release -o out in the builder, then dotnet
.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT; the server must bind 0.0.0.0 on PORT. - Read DATABASE_URL at runtime. Open connections from the environment inside handlers or a pool; omit DATABASE_URL to auto-provision a managed database or pass --env DATABASE_URL=... for an existing one.
- Verify. Fetch the live URL and /p/relational-records 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”
✓ relational-records check from the example· http get/p/relational-records → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); for this guide: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok).
Tested examples
- ASP.NET Core pattern fixture. Verified database connection on ASP.NET Core.
What it doesn’t cover
- Verified on the dotnet-10 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.