## Host storefront with ASP.NET Core: authorized file delivery

### Summary
Deploy a storefront built with ASP.NET Core on Ample using the generated downloads 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on ASP.NET Core: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the storefront-specific behavior as your application code.

### Representative Queries
- Host storefront with ASP.NET Core: authorized file delivery
- Where can I host Storefront built with ASP.NET Core?
- I need a file entitlement model and an application-enforced download authorization flow.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

### 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.
3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; operations are verified by canary.

### 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).
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
- An Ample account token with servers:write, databases:read, buckets: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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent.
3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.
4. **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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build`.

### Examples
- **Title:** ASP.NET Core pattern fixture  
  **Description:** Multi-pattern ASP.NET Core app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  **Source Ref:** tests/deploy-canaries/asp-net-core-patterns

### Success Checks
1. App responds on its public URL, expected: ample canary asp net core patterns.
2. Generated-downloads self-test, expected: export=ok rows=3 (with ?token=...; 401 without).

### 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 storefront itself (your export formats, retention policy and entitlement model) is application code and was not separately tested.

### Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.0
- **Components:**  
   - App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0  
   - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0  
- **Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Evidence Summary
- **Kind:** canary_run  
  **Summary:** ASP.NET Core pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.  
  **Observed At:** 2026-09-21T01:15:54Z
  **Scope:**  
  - Checks: [/p/generated-downloads]  
  - Pattern: pattern:generated-downloads  
  - Template: dotnet-10

### Next Actions
- **Action:** Browse the catalog index  
  **Method:** GET  
  **Path:** /v1/catalog  
- **Action:** Search published recipes by intent  
  **Method:** POST  
  **Path:** /v1/catalog/search
- **Action:** Prepare a side-effect-free deployment plan  
  **Method:** POST  
  **Path:** /v1/catalog/plan
- **Action:** Read the existing agent authentication setup  
  **Method:** GET  
  **Path:** /mcp/setup
- **Action:** Browse Storefront  
  **Method:** GET  
  **Path:** /v1/catalog/nodes/workload%3Astorefront
- **Action:** Browse ASP.NET Core  
  **Method:** GET  
  **Path:** /v1/catalog/nodes/stack%3Aframework-asp-net-core
- **Action:** Browse Generated downloads  
  **Method:** GET  
  **Path:** /v1/catalog/nodes/pattern%3Agenerated-downloads
- **Action:** Browse Deploy web app  
  **Method:** GET  
  **Path:** /v1/catalog/nodes/intent%3Adeploy-web-app