# Host order tracking with ASP.NET Core: public product media

Deploy a order tracking built with ASP.NET Core on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on ASP.NET Core: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the order tracking-specific behavior as your application code.

## Representative Queries
- Host order tracking with ASP.NET Core: public product media
- Where can I host Order tracking built with ASP.NET Core?
- I need product-to-object mappings and a tested public media delivery path.

## Framework and Workload
- **Framework:** ASP.NET Core
- **Workload:** Order tracking

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

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

4. **CDN** 
   - Status: verified
   - Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## 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 and a second, published bucket for public assets (CDN_*)
- 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 public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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. Publish only the bucket that serves public assets and reference its CDN URL.

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=... --env CDN_PUBLIC_URL=...`

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) 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
- **app responds on its public URL**  
   Kind: http_get  
   Path: /  
   Expect: ample canary asp net core patterns

- **public-media-library self-test**  
   Kind: http_get  
   Path: /p/public-media-library  
   Expect: a CDN URL whose content is served publicly

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.0
- **Authoritative:** true
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

**Components:**  
1. **app server**  
   Size: s-1vcpu-1gb  
   Quantity: 1.0  
   Monthly Amount: 5.0

2. **managed PostgreSQL database**  
   Size: 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. Buckets are allocation-priced per quota and not included.

## 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 order tracking itself (your media processing, object layout and cache 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

## Evidence Summary
1. **Canary Run**  
   Summary: ASP.NET Core pattern fixture deployed on Ample  
   Observed At: 2026-09-21T01:15:54Z  
   Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)  
   Expires At: 2027-03-20T01:15:54Z

2. **Canary Run**  
   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  
   Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)  
   Expires At: 2027-03-19T23:34:47Z

## Next Actions
1. **Browse the catalog index**  
   Method: GET  
   Relative Path: /v1/catalog

2. **Search published recipes by intent, stack and constraints**  
   Method: POST  
   Relative Path: /v1/catalog/search

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   Method: POST  
   Relative Path: /v1/catalog/plan

4. **Read the existing agent authentication setup**  
   Method: GET  
   Relative Path: /mcp/setup

5. **Browse Order tracking**  
   Method: GET  
   Relative Path: /v1/catalog/nodes/workload%3Aorder-tracking

6. **Browse ASP.NET Core**  
   Method: GET  
   Relative Path: /v1/catalog/nodes/stack%3Aframework-asp-net-core

7. **Browse Public media library**  
   Method: GET  
   Relative Path: /v1/catalog/nodes/pattern%3Apublic-media-library

8. **Browse Deploy web app**  
   Method: GET  
   Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app