Host Client Portal with ASP.NET Core: Application Activity History

Deploy a client portal built with ASP.NET Core on Ample using the transactional workflows 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.

Summary

• Verified on ASP.NET Core: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).
• Not separately tested: your domain records, validation rules, and concurrency policy; treat the client portal-specific behavior as your application code.

Representative Queries

• Host client portal with ASP.NET Core: application activity history
• Where can I host Client portal built with ASP.NET Core?
• I need an application-owned event schema and tested history queries; not native platform audit logs.

Prerequisites

1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with servers:write, databases: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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). 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/transactional-workflows) 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
• transactional-workflows self-test
  • Kind: http_get
  • Path: /p/transactional-workflows
  • Expect: tx=ok history=2 conflict=rejected

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 client portal itself (your domain records, validation rules, and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Monthly Amount: $10.00 (USD)
• Details:
  • App Server:
    • Size: s-1vcpu-1gb
    • Monthly Amount: $5.00
  • Managed PostgreSQL Database:
    • Size: s-1vcpu-1gb
    • Monthly Amount: $5.00

Evidence Summary

• Canary Run Summary:
  Deployed on Ample with checks passed for transactional-workflows and configuration-secrets. The pattern proof includes an optimistic version check and an event row written in the same transaction.

Formats

• HTML Format
• Markdown Format
• JSON Format