# Connect Postgres for ASP.NET Core

## Summary
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 .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.

## Representative Queries
- Connect Postgres for ASP.NET Core
- Where can I host Connect Postgres built with ASP.NET Core?
- I need driver setup, connection settings, secret handling and a real connection test.

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

## Workflow Steps
1. **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.
2. **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.
3. **Verify**  
   Fetch the live URL and `/p/relational-records` on the example; on failure read the build and runtime logs.  
   Command: `ample logs --kind build`

## Success Checks
- **App responds on its public URL**  
  Kind: `http_get`  
  Path: `/`  
  Expect: `ample canary asp net core patterns`
- **Relational-records check from the example**  
  Kind: `http_get`  
  Path: `/p/relational-records`  
  Expect: `see the pattern fixture checks`

## Limitations
- Verified on the dotnet-10 template at size `s-1vcpu-1gb`; other sizes and ASP.NET Core major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision `1ac5595375130d45290090e82ed0f554ccd45405-dirty`  
- **Components**:
  - App server  
    - Size: `s-1vcpu-1gb`  
    - Quantity: 1.0  
    - Monthly Amount: 5.0
  - Managed PostgreSQL database  
    - Size: `s-1vcpu-1gb`  
    - Quantity: 1.0  
    - Monthly Amount: 5.0  
- **Note**: Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Kind**: canary_run  
- **Summary**: ASP.NET Core pattern fixture deployed on Ample; for this guide: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok).  
- **Observed At**: 2026-09-21T01:15:54Z  
- **Implementation Revision**: `50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)`  
- **Expires At**: 2027-03-20T01:15:54Z  
- **Scope**:  
  - Checks: [`/p/relational-records`]  
  - Template: dotnet-10

## Next Actions
- **Browse the catalog index**  
  Action ID: `browse-catalog`  
  Method: `GET`  
  Relative Path: `/v1/catalog`
- **Search published recipes by intent, stack and constraints**  
  Action ID: `search-recipes`  
  Method: `POST`  
  Relative Path: `/v1/catalog/search`  
  Parameters: `{