## Host member portal with ASP.NET Core: application activity history

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

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

### Resource Requirements
- **compute**
- **postgres**

### Infrastructure Requirements
1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **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
- **Framework:** ASP.NET Core  
- **Workload:** Member portal  
- **Release Status:** published  
- **Support Status:** verified  
- **Execution Status:** ready  
- **Docs Only:** false

### 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**  
   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.
   ```bash
   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`.
   ```bash
   ample logs --kind build
   ```

### Examples
- **Title:** ASP.NET Core pattern fixture  
  **Description:** Multi-pattern ASP.NET Core app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  **Source Reference:** tests/deploy-canaries/asp-net-core-patterns

### Success Checks
- **Description:** app responds on its public URL  
  **Kind:** http_get  
  **Path:** /  
  **Expectation:** ample canary asp net core patterns
- **Description:** transactional-workflows self-test  
  **Kind:** http_get  
  **Path:** /p/transactional-workflows  
  **Expectation:** 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 member 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.
- 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  
- **Authoritative:** true  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components:**
  1. **Name:** app server  
     **Size:** s-1vcpu-1gb  
     **Quantity:** 1.0  
     **Monthly Amount:** 5.0  
  2. **Name:** 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.

### Github Evidence Summary
- **Kind:** canary_run  
  **Summary:** ASP.NET Core pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
  **Observed At:** 2026-09-21T01:15:54Z  
  **Implementation Revision:** 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)  
  **Expires At:** 2027-03-20T01:15:54Z

### MCP Binding
- **Registry Ref:** mcp:ample_deploy  
- **Tool Name:** ample_deploy  
- **Schema Hash:** 876465fce906da0c224d62961d3343064108ebe30af80cf1b87094974e948853  
- **Observed At:** 2026-09-21T03:19:59.461917+00:00  
- **Implementation Revision:** 49962bcade4f  
- **Required Scopes:** servers:write, databases:read  
- **Binding State:** current

### Next Actions
1. **Action ID:** browse-catalog  
   **Label:** Browse the catalog index  
   **Operation ID:** catalog_index  
   **Method:** GET  
   **Relative Path:** /v1/catalog  
   **Requires Authentication:** false

2. **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 member portal with ASP.NET Core: application activity history"}  
   **Requires Authentication:** false

3. **Action ID:** plan:page:recipes:member-portal:asp-net-core:activity-history  
   **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:member-portal:asp-net-core:activity-history","recipeRevision":"r1"}}  
   **Requires Authentication:** true

4. **Action ID:** auth-setup  
   **Label:** Read the existing agent authentication setup  
   **Operation ID:** existing_auth_setup  
   **Method:** GET  
   **Relative Path:** /mcp/setup  
   **Requires Authentication:** false

5. **Action ID:** browse:workload:member-portal  
   **Label:** Browse Member portal  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/workload%3Amember-portal  
   **Parameters:** {"nodeId":"workload:member-portal"}  
   **Requires Authentication:** false

6. **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"}  
   **Requires Authentication:** false

7. **Action ID:** browse:pattern:transactional-workflows  
   **Label:** Browse Transactional workflows  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/pattern%3Atransactional-workflows  
   **Parameters:** {"nodeId":"pattern:transactional-workflows"}  
   **Requires Authentication:** false

8. **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"}  
   **Requires Authentication:** false