Configure build and start for ASP.NET Core · Ample Computer

Configure build and start for ASP.NET Core

Build and start for a ASP.NET Core app on Ample. Verified on ASP.NET Core: the app built and started with the documented commands and answered on its public HTTPS 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.

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. Deploy. Run the synchronous deploy once and read the result.

    $ ample deploy . --name <app-name> --public
    
  3. Verify. Fetch the live URL 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”

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: the app built and started with the documented commands and answered on its public HTTPS URL.

Tested examples

What it doesn’t cover