### Host appointment booking with ASP.NET Core: data exports

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

#### Representative Queries
- Host appointment booking with ASP.NET Core: data exports
- Where can I host Appointment booking built with ASP.NET Core?
- I need a scoped export format, artifact generation and authorized download procedure.

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

#### Infrastructure Requirements
1. **Compute**  
   Verified: 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**  
   Verified: 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**  
   Verified: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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

#### 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 and run them with --release-command.
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.
   ```bash
   ample deploy . --name <app-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` then `--kind runtime`.
   ```bash
   ample logs  --kind build
   ```

#### 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 appointment booking itself (your export formats, retention policy and entitlement model) 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

#### Cost Estimate
- **Monthly Amount**: 10.0 USD (authoritative)
  - Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
  - Components:
    - app server (s-1vcpu-1gb)  : $5.00
    - managed PostgreSQL database (s-1vcpu-1gb) : $5.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.

#### Success Checks
1. **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary asp net core patterns
2. **Generated-downloads self-test**  
   - Kind: http_get  
   - Path: /p/generated-downloads  
   - Expect: export=ok rows=3 (with ?token=...; 401 without)

#### Evidence Summary
1. **ASP.NET Core pattern fixture**  
   - Summary: ASP.NET Core pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller.
   - Observed At: 2026-09-21T01:15:54Z  
   - Expires At: 2027-03-20T01:15:54Z

2. **Migration Test Summary**  
   - Summary: 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  
   - Expires At: 2027-03-19T23:34:47Z

### Next Actions
- **Browse the catalog index**  
  Action: `GET /v1/catalog`
- **Search published recipes by intent, stack, and constraints**  
  Action: `POST /v1/catalog/search`
- **Prepare a side-effect-free deployment plan for an authorized project**  
  Action: `POST /v1/catalog/plan`
- **Read the existing agent authentication setup**  
  Action: `GET /mcp/setup`
- **Browse Appointment booking**  
  Action: `GET /v1/catalog/nodes/workload%3Aappointment-booking`
- **Browse ASP.NET Core**  
  Action: `GET /v1/catalog/nodes/stack%3Aframework-asp-net-core`
- **Browse Generated downloads**  
  Action: `GET /v1/catalog/nodes/pattern%3Agenerated-downloads`
- **Browse Deploy web app**  
  Action: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`