### Host community forum with ASP.NET Core: tenant-scoped workspaces

#### Summary
Deploy a community forum built with ASP.NET Core on Ample using the multi-tenant relational data 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 tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the community forum-specific behavior as your application code.

#### Representative Queries
- Host community forum with ASP.NET Core: tenant-scoped workspaces
- Where can I host Community forum built with ASP.NET Core?
- I need an explicit tenant model and application-enforced tenant isolation tests.

#### Resource Requirements
- **Compute**
- **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.

#### 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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). 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 <YOUR_APP_NAME> --public`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (`/p/multi-tenant-relational-data`) from the example; then run your own checks. On failure read `ample logs <YOUR_APP_NAME> --kind build` then `--kind runtime`.
   
   Command: `ample logs <YOUR_APP_NAME> --kind build`

#### Examples
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose multi-tenant relational data module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

#### Success Checks
- **App responds on its public URL**:  `http_get /` expecting response `ample canary asp net core patterns`
- **Multi-tenant-relational-data self-test**:  `http_get /p/multi-tenant-relational-data` expecting response `tenant_isolation=ok`

#### 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 tenant model, membership and per-tenant authorization) 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` at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **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`
- **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.