page:recipes:vendor portal:asp net core:public profiles

Host vendor portal with ASP.NET Core: public profile assets

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

Representative Queries

• Host vendor portal with ASP.NET Core: public profile assets
• Where can I host Vendor 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

1. Compute

   • Status: Verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.

2. Postgres

   • Status: Verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database.

3. S3-compatible object storage

   • Status: Verified
   • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

4. CDN

   • Status: Verified
   • Summary: The CDN host serves objects from published buckets.

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.

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.

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. Command: ample deploy . --name --public ...

5. Verify

   • Fetch the live URL and perform checks. Command: ample logs --kind build.

Examples

• ASP.NET Core pattern fixture
  • Description: Multi-pattern ASP.NET Core app whose public image delivery module was checked live.

Success Checks

1. app responds on its public URL
2. public-media-library self-test
3. private-document-library self-test

Limitations

• Verified on the dotnet-10 template at s-1vcpu-1gb; other sizes and templates not verified.

Cost Estimate

• Monthly Amount: $10.00
  • Components:
    • app server (s-1vcpu-1gb): $5.00
    • managed PostgreSQL database: $5.00

Evidence Summary

• Canary Run: ASP.NET Core pattern fixture deployed on Ample; checks passed for public and private libraries.