# Host Recruiting Tracker with ASP.NET Core: Downloadable Reports

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

## Representative Queries
- Host recruiting tracker with ASP.NET Core: downloadable reports
- Where can I host Recruiting tracker built with ASP.NET Core?
- I need an export query, generated artifact retention and authorized download flow.

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

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

### S3-compatible Object Storage
Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Framework
ASP.NET Core

## Workload
Recruiting tracker

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

## 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 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.
   - 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` then `--kind runtime`.
   - Command: ample logs  --kind build

## Examples
### 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 Reference: tests/deploy-canaries/asp-net-core-patterns

## Success Checks
- App responds on its public URL (Path: /, Expect: ample canary asp net core patterns)
- Generated-downloads self-test (Path: /p/generated-downloads, Expect: 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 recruiting tracker 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 verified.

## Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Authority: 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.

## Evidence Summary
- **Canary Run**
   - Summary: 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 generated-downloads and configuration-secrets.  
   - Observed At: 2026-09-21T01:15:54Z  
   - Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)  
   - Expires At: 2027-03-20T01:15:54Z  
   - Scope: { "checks": ["/p/generated-downloads"], "pattern": "pattern:generated-downloads", "template": "dotnet-10" }

- **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 
   - Scope: { "pattern": "pattern:generated-downloads" }

## Next Actions
1. **Browse the Catalog Index**  
   - Operation ID: catalog_index  
   - Method: GET  
   - Relative Path: /v1/catalog

2. **Search Published Recipes**  
   - Operation ID: search_recipes  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
   - Parameters: { "body": { "limit": 5, "query": "Host recruiting tracker with ASP.NET Core: downloadable reports" } }

3. **Prepare a Deployment Plan**  
   - Operation ID: plan_deployment  
   - Method: POST  
   - Relative Path: /v1/catalog/plan  
   - Parameters: { "body": { "inputs": {}, "projectId": "", "recipeId": "page:recipes:recruiting-tracker:asp-net-core:report-exports", "recipeRevision": "r1" } }

4. **Read Existing Agent Authentication Setup**  
   - Operation ID: existing_auth_setup  
   - Method: GET  
   - Relative Path: /mcp/setup

5. **Browse Recruiting Tracker**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/workload%3Arecruiting-tracker  
   - Parameters: { "nodeId": "workload:recruiting-tracker" }

6. **Browse ASP.NET Core**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-asp-net-core  
   - Parameters: { "nodeId": "stack:framework-asp-net-core" }

7. **Browse Generated Downloads**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads  
   - Parameters: { "nodeId": "pattern:generated-downloads" }

8. **Browse Deploy Web App**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app  
   - Parameters: { "nodeId": "intent:deploy-web-app" }