## Host appointment booking with ASP.NET Core: structured data imports

### Summary
Deploy a appointment booking built with ASP.NET Core on Ample using the bulk import staging 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. Verified on ASP.NET Core: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the appointment booking-specific behavior as your application code.

### Framework
ASP.NET Core

### Workload
Appointment booking

### Execution Status
Ready

### Workflow Steps
1. **Build and start**  
   `dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT. The server must bind `0.0.0.0` on PORT.

2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Copy the approach into your schema; keep migrations idempotent and run them with `--release-command`.

3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as `--env` values. Use path-style addressing. Keep private data in an unpublished bucket.

4. **Deploy**  
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
   ```bash
   ample deploy . --name [YOUR_APP_NAME] --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   ```

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (`/p/bulk-import-staging`) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   ```bash
   ample logs --kind build
   ```

### Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates and ASP.NET Core major versions are not verified.
- The appointment booking itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- **Monthly Amount**: $10.00  
  - App server (s-1vcpu-1gb): $5.00  
  - Managed PostgreSQL database (s-1vcpu-1gb): $5.00

### Success Checks
- App responds on its public URL. Expect response: `ample canary asp net core patterns`
- Bulk-import-staging self-test. Expect response: `imported=2 rejected=1 restart=ok`

### Tested Configuration
- **Template**: dotnet-10  
- **Runtime**: dotnet  
- **Size**: s-1vcpu-1gb  
- **Build Command**: `dotnet publish -c Release -o out`  
- **Start Command**: `ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll`