Host help desk with ASP.NET Core: relational workspace data · Ample Computer

Host help desk with ASP.NET Core: relational workspace data

Deploy a help desk 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). The help desk-specific behavior (your record schema, states and access rules) is your application code on that verified basis.

supportverifiedreleasepublishedagent runready

VerifiedNovember 6, 2026

What it runs on

You need

An 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

Exact tested configuration

builddotnet publish -c Release -o out

runtimedotnet

sizes-1vcpu-1gb

startASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll

templatedotnet-10

Steps

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

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

  1. 3

Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

   $ ample deploy . --name <app-name> --public
  1. 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 <deployment_id> --kind build then --kind runtime.

   $ ample logs <deployment_id> --kind build

How it was checked

✓app responds on its public URL· http get/ → “ample canary asp net core patterns”

✓relational-records self-test· http get/p/relational-records → “records=ok transitions=true isolation=true”

Evidence

  1. November 6, 2026 · canary run

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 relational-records and configuration-secrets. Pattern proof: 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).

  1. November 5, 2026 · canary run

The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.

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

What it doesn’t cover

Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture.

The pattern checks verified the platform side; the help desk itself (your record schema, states and access rules) is your application code.

Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.