# Configure environment and secrets for ASP.NET Core

Configuration and secrets for a ASP.NET Core app on Ample. Verified on ASP.NET Core: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

## You need

- An ASP.NET Core project (dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT)
- An Ample account token with servers:write

## Exact tested configuration

- build  
  dotnet publish -c Release -o out
- runtime  
  dotnet
- sizes  
  1vcpu-1gb
- start  
  ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll
- template  
  dotnet-10

## 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. **Pass values on deploy.** Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.
   
   ```sh
   $ ample deploy . --name <app-name> --public --env MY_SECRET=...
   ```

3. **Verify.** Fetch the live URL and /p/configuration-secrets on the example; on failure read the build and runtime logs.
   
   ```sh
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary asp net core patterns”  
✓ configuration-secrets check from the example· http get/p/configuration-secrets → “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: an --env value delivered encrypted and reported as present without being echoed (secret=set).

## Tested examples

- **ASP.NET Core pattern fixture.** Verified configuration and secrets on ASP.NET Core.

## What it doesn’t cover

- Verified on the dotnet-10 template at s-1vcpu-1gb.
