Deliver public assets through CDN for ASP.NET Core · Ample Computer

Deliver public assets through CDN for ASP.NET Core

Cdn assets for a ASP.NET Core app on Ample. Verified on ASP.NET Core: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start.
    dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT; the server must bind 0.0.0.0 on PORT.

  2. Publish a bucket for public assets.
    Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.

    $ ample bucket publish <bucket-name>
    
  3. Verify.
    Fetch the live URL and /p/versioned-static-assets on the example; on failure read the build and runtime logs.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL · http get / → “ample canary asp net core patterns”
✓ versioned-static-assets check from the example · http get /p/versioned-static-assets → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run

    ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

Tested examples

What it doesn’t cover