page:recipes:recruiting tracker:asp net core:report exports

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

Resource Requirements

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

Tested Configuration

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

Success Checks

Limitations

Cost Estimate

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

Evidence Summary

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" }