page:recipes:recruiting tracker:asp net core:relational workspace

Host recruiting tracker with ASP.NET Core: relational workspace data

Deploy a recruiting tracker built with ASP.NET Core on Ample using the relational records 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. Verified on ASP.NET Core: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the recruiting tracker-specific behavior as your application code.

Representative Queries

• Host recruiting tracker with ASP.NET Core: relational workspace data
• Where can I host Recruiting tracker built with ASP.NET Core?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• primitive:compute
• primitive:postgres

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.

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)
• An Ample account token with servers:write, databases: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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. 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
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) 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: Multi-pattern ASP.NET Core app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL - Path: / - Expect: ample canary asp net core patterns
• Relational-records self-test - Path: /p/relational-records - Expect: records=ok transitions=true isolation=true

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 record schema, states and access rules) 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.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App Server: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  • Managed PostgreSQL Database: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 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

• Kind: canary_run
  Summary: ASP.NET Core pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.
  Observed At: 2026-09-21T01:15:54Z
• Kind: 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

Next Actions

• Action ID: browse-catalog

  • Label: Browse the catalog index
  • Operation ID: catalog_index
  • Method: GET
  • Relative Path: /v1/catalog

• Action ID: search-recipes

  • Label: Search published recipes by intent, stack and constraints
  • Operation ID: search_recipes
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Parameters: {"body":{"limit":5,"query":"Host recruiting tracker with ASP.NET Core: relational workspace data"}}

• Action ID: plan:page:recipes:recruiting-tracker:asp-net-core:relational-workspace

  • Label: Prepare a side-effect-free deployment plan for an authorized project
  • Operation ID: plan_deployment
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:recruiting-tracker:asp-net-core:relational-workspace","recipeRevision":"r1"}}

• Action ID: auth-setup

  • Label: Read the existing agent authentication setup
  • Operation ID: existing_auth_setup
  • Method: GET
  • Relative Path: /mcp/setup

• Action ID: browse:workload:recruiting-tracker

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

• Action ID: browse:stack:framework-asp-net-core

  • Label: 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"}}

• Action ID: browse:pattern:relational-records

  • Label: Browse Relational records
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/pattern%3Arelational-records
  • Parameters: {"nodeId":"pattern:relational-records"}}

• Action ID: browse:intent:deploy-web-app

  • Label: 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"}}