## Host digital downloads with ASP.NET Core: relational catalog data

### Summary
Deploy a digital downloads built with ASP.NET Core on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the digital downloads-specific behavior as your application code.

### Representative Queries
- Host digital downloads with ASP.NET Core: relational catalog data
- Where can I host Digital downloads built with ASP.NET Core?
- I need catalog tables, transactional update logic and application-level access boundaries.

### Resource Requirements
- **primitive:compute**
- **primitive: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
- 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)
- 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**: The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). 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 --public`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   - Command: `ample logs --kind build`

### Examples
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
- App responds on its public URL
  - Kind: `http_get`
  - Path: `/`
  - Expect: ample canary asp net core patterns
- Transactional-workflows self-test
  - Kind: `http_get`
  - Path: `/p/transactional-workflows`
  - Expect: `tx=ok history=2 conflict=rejected`

### 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 digital downloads itself (your domain records, validation rules and concurrency policy) 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.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, monthlyAmount=5.0
  - **managed PostgreSQL database**: size=s-1vcpu-1gb, quantity=1.0, monthlyAmount=5.0
- **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.

### Evidence Summary
- **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); checks passed for transactional-workflows and configuration-secrets.
  - Observed At: 2026-09-21T01:15:54Z
- **Canary Run**: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.
  - Observed At: 2026-09-20T23:34:47Z

### Formats
- **HTML**: [Link](/content/recipes/digital-downloads/asp-net-core/relational-catalog/index.html)
- **Markdown**: [Link](/content/recipes/digital-downloads/asp-net-core/relational-catalog.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Adigital-downloads%3Aasp-net-core%3Arelational-catalog)

### Next Actions
1. **Browse the catalog index**
   - Action ID: `browse-catalog`
   - Method: GET
   - Relative Path: `/v1/catalog`
2. **Search published recipes by intent, stack and constraints**
   - Action ID: `search-recipes`
   - Method: POST
   - Relative Path: `/v1/catalog/search`
   - Parameters: `{ "body": {"limit":5,"query":"Host digital downloads with ASP.NET Core: relational catalog data"} }`
3. **Prepare a side-effect-free deployment plan for an authorized project**
   - Action ID: `plan:page:recipes:digital-downloads:asp-net-core:relational-catalog`
   - Method: POST
   - Relative Path: `/v1/catalog/plan`
   - Parameters: `{ "body": {"inputs":{},"projectId":"","recipeId":"page:recipes:digital-downloads:asp-net-core:relational-catalog","recipeRevision":"r1"} }`
4. **Read the existing agent authentication setup**
   - Action ID: `auth-setup`
   - Method: GET
   - Relative Path: `/mcp/setup`
