# Host member portal with ASP.NET Core: public profile assets

Deploy a member 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.

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

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

## Requirement
- 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.
  - **S3-compatible object storage:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
  - **CDN:** 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 .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. **Wire Object Storage**: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. **Deploy**: Run the synchronous deploy once and read the result.
5. **Verify**: Fetch the live URL and test the pattern self-test routes.

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

## Limitations
- Verified on dotnet-10 template; other sizes and ASP.NET Core versions not verified.
- The member portal's application code was not separately tested.
- Apps auto-pause when idle.

## Cost Estimate
- **Monthly Amount**: $10.00
- **Items**:
  - App server: 1 x $5.00
  - Managed PostgreSQL database: 1 x $5.00
- Note: Buckets are allocation-priced per quota and not included.

## Next Actions
- Browse the catalog index.
- Search published recipes.
- Prepare a side-effect-free deployment plan for an authorized project.