Host community forum with ASP.NET Core: application activity history

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

Representative Queries

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

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

Compute

• Status: verified
• Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

Postgres

• Status: verified
• Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

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

Workflow Steps

1. Build and start

   • Command: dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.

2. Implement the pattern on PostgreSQL

   • Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. Deploy

   • Command: ample deploy . --name --public

4. Verify

   • Command: ample logs --kind build

Success Checks

• App responds on its public URL

  • Check path: /
  • Expect: ample canary asp net core patterns

• Transactional-workflows self-test

  • Check 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 community forum 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)
• Components:
  • App Server: Size s-1vcpu-1gb, Quantity 1.0, Monthly Amount 5.0
  • Managed PostgreSQL Database: Size s-1vcpu-1gb, Quantity 1.0, Monthly Amount 5.0

Evidence Summary

• Canary Run: ASP.NET Core pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
• Canary Run: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.