### Host project tracker with ASP.NET Core: relational workspace data

Deploy a project tracker built with ASP.NET Core on Ample using the relational records pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on ASP.NET Core: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the project tracker-specific behavior as your application code.

#### Representative Queries
- Host project tracker with ASP.NET Core: relational workspace data
- Where can I host Project tracker built with ASP.NET Core?
- I need a workspace-specific schema, state transitions and access rules.

#### Resource Requirements
- Compute
- Postgres

#### Infrastructure Requirements
- **Compute**  
  Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**  
  Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

#### Prerequisites
- A ASP.NET Core project that builds and starts with the documented commands (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 (auto-provisioned when omitted, or supplied with --env)
- 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. **Implement the pattern on PostgreSQL**  
   Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Deploy**  
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op. 
   `ample deploy . --name --public`
4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks.
   `ample logs --kind build`

#### Examples
- **ASP.NET Core pattern fixture**  
  Multi-pattern ASP.NET Core app whose relational records module was checked live.

#### Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates and ASP.NET Core major versions are not verified.

#### Cost Estimate
- **Monthly Amount:** 10.0 USD
  - **App Server:** 5.0 USD (s-1vcpu-1gb)
  - **Managed PostgreSQL Database:** 5.0 USD (s-1vcpu-1gb)
  - Note: Apps and databases auto-pause when idle.

#### Known Unknowns
- Region availability is unknown until a verified region fact is recorded.

#### Formats
- **HTML:** [View here](/content/recipes/project-tracker/asp-net-core/relational-workspace/index.html)
- **Markdown:** [View here](/content/recipes/project-tracker/asp-net-core/relational-workspace.md)
- **JSON:** [View here](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aproject-tracker%3Aasp-net-core%3Arelational-workspace)