## Host help desk with ASP.NET Core: relational workspace data

Deploy a help desk 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 help desk-specific behavior as your application code.

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

### Resource Requirements
- Compute
- Postgres

### Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **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.

### Framework
- ASP.NET Core

### Workload
- Help desk

### Release Status
- Published

### Support Status
- Verified

### Execution Status
- Ready

### Prerequisites
1. An 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with `servers:write`, `databases:read`

### Tested Configuration
- **Template**: dotnet-10
- **Runtime**: dotnet
- **Size**: s-1vcpu-1gb
- **Build**: dotnet publish -c Release -o out
- **Start**: ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll

### 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**: The fixture's module implements relational records: 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). 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.
   - Command: `ample deploy . --name <name> --public`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   - Command: `ample logs --kind build`

### Success Checks
1. App responds on its public URL
   - Path: `/`
   - Expect: `ample canary asp net core patterns`
2. Relational-records self-test
   - Path: `/p/relational-records`
   - Expect: `records=ok transitions=true isolation=true`

### 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.
- The help desk itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.
- **Components**:
  - App server: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
  - Managed PostgreSQL database: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00

### Evidence Summary
1. **Canary Run**: ASP.NET Core pattern fixture deployed on Ample.
   - Summary: Checks passed for relational-records and configuration-secrets.

2. **Canary Run**: The same ASP.NET Core app deployed with a --release-command migration.
   - Summary: The marker it created was readable after activation.

### Last Verified At
- 2026-09-21T01:15:54Z

### Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.