# Host Client Portal with ASP.NET Core: Public Profile Assets

Deploy a client portal built with ASP.NET Core on Ample using the public image delivery 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`, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host.

## Summary
Verified on ASP.NET Core: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the client portal-specific behavior as your application code.

### Representative Queries
- Host client portal with ASP.NET Core: public profile assets
- Where can I host Client portal built with ASP.NET Core?
- I need separate public profile media from private data, with CDN cache rules.

## Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive:s3-compatible-object-storage`
- `primitive:cdn`

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

### S3-compatible Object Storage
- **Status**: Verified
- **Summary**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### CDN
- **Status**: Verified
- **Summary**: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## Workflow Steps
1. **Build and Start**  
   `dotnet publish -c Release -o out` in the builder, then `dotnet <your_app>.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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 
   Copy the approach into your schema; keep migrations idempotent and run them with `--release-command`.

3. **Wire Object Storage**  
   Create the bucket(s), then pass endpoint, region, bucket, and keys as `--env` values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.

4. **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 <name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...`

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) `/p/public-media-library`, `/p/private-document-library` from the example; then run your own checks.  
   On failure read `ample logs <your_command> --kind build` then `--kind runtime`.  
   Command: `ample logs --kind build`

## Success Checks
- App responds on its public URL
- Public-media-library self-test
- Private-document-library self-test

## 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 image processing and profile-media rules) is application code and was not separately tested; the pattern checks are what was verified.
- Other limitations based on app deployment and configuration nuances are noted.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server: s-1vcpu-1gb - $5.0
  - Managed PostgreSQL database: s-1vcpu-1gb - $5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Formats
- [HTML Format](/content/recipes/client-portal/asp-net-core/public-profiles/index.html)  
- [Markdown Format](/content/recipes/client-portal/asp-net-core/public-profiles.md)  
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aclient-portal%3Aasp-net-core%3Apublic-profiles)

## Next Actions
- [Browse the catalog index](https://api.ample.com/v1/catalog)
- [Search published recipes](https://api.ample.com/v1/catalog/search)
- [Prepare deployment plan](https://api.ample.com/v1/catalog/plan)  
- [Read existing authentication setup](https://api.ample.com/mcp/setup)  
- [Browse Client portal](https://api.ample.com/v1/catalog/nodes/workload%3Aclient-portal)  
- [Browse ASP.NET Core](https://api.ample.com/v1/catalog/nodes/stack%3Aframework-asp-net-core)  
- [Browse Public image delivery](https://api.ample.com/v1/catalog/nodes/pattern%3Apublic-image-delivery)  
- [Browse Deploy web app](https://api.ample.com/v1/catalog/nodes/intent%3Adeploy-web-app)