page:recipes:community forum:asp net core:public profiles

Host community forum with ASP.NET Core: public profile assets

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

Representative Queries

Host community forum with ASP.NET Core: public profile assets
Where can I host Community forum 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: Apps run in isolated x86_64 Firecracker microVMs.
Postgres: Managed PostgreSQL 16 runs in its own microVM.
S3-compatible object storage: Buckets are S3-compatible with issued credentials.
CDN: The CDN host serves objects from published buckets.

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.
A bucket from ample bucket create with encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*).
An Ample account token with appropriate permissions.

Workflow Steps

Build and start: Execute dotnet publish -c Release -o out.
Implement the pattern on PostgreSQL: Ensure public image delivery
Wire object storage: Create buckets and set environment variables accordingly.
Deploy: Run ample deploy . --name ... --public ....
Verify: Fetch live URL and execute self-test routes.

Limitations

Verified on the dotnet-10 template; other versions may not be.
Community forum image processing was not separately tested.

Cost Estimate

Monthly Amount: 10.0 USD
- App server: 5.0 USD
- Managed PostgreSQL database: 5.0 USD

Success Checks

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