## Host Storefront with ASP.NET Core: Relational Catalog Data

### Summary
Deploy a storefront 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 storefront-specific behavior as your application code.

### Representative Queries
- Host storefront with ASP.NET Core: relational catalog data
- Where can I host Storefront built with ASP.NET Core?
- I need catalog tables, transactional update logic, and application-level access boundaries.

### Resource Requirements
- **Compute**
- **Postgres**

### Infrastructure Requirements
1. **Compute**  
   Managed Compute resources auto-pause when idle and wake on request; sizes vary based on VM sizes.
2. **Postgres**  
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database without a supplied DATABASE_URL.

### Framework
**ASP.NET Core**

### Workload
**Storefront**

### Release Status
**Published**  
### Support Status
**Verified**  
### Execution Status
**Ready**

### Prerequisites
- 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

### 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**  
   Command: 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. 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

### Examples
- **ASP.NET Core Pattern Fixture**: Multi-pattern ASP.NET Core app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
- App responds on its public URL  
- Transactional-workflows self-test

### Limitations
- Verified on the dotnet-10 template at size s-1vcpu-1gb; other sizes, templates, and ASP.NET Core major versions are not verified.

### Cost Estimate
- **Monthly Amount**: $10.00  
- Components:  
   1. App Server: s-1vcpu-1gb - $5.00  
   2. Managed PostgreSQL Database: s-1vcpu-1gb - $5.00
   
### Last Verified
2026-09-21T01:15:54Z

### Next Actions
1. [Browse the catalog index](/v1/catalog)  
2. [Search published recipes by intent](/v1/catalog/search)  
3. [Prepare a side-effect-free deployment plan](/content/site-root.html)  
4. [Read the existing agent authentication setup](/mcp/setup)  
5. [Browse Storefront](/v1/catalog/nodes/workload%3Astorefront)  
6. [Browse ASP.NET Core](/v1/catalog/nodes/stack%3Aframework-asp-net-core)  
7. [Browse Transactional Workflows](/v1/catalog/nodes/pattern%3Atransactional-workflows)  
8. [Browse Deploy Web App](/v1/catalog/nodes/intent%3Adeploy-web-app)

### Evidence Summary
- **Canary Run**  
   Deployed on Ample and checked for transactional workflows.