## Host project tracker with ASP.NET Core: CSV imports

### Summary
Deploy a project tracker 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 project tracker-specific behavior as your application code.

### Framework
ASP.NET Core

### Workload
Project tracker

### Release Status
published

### Support Status
verified

### Execution Status
ready

### Prerequisites
- A ASP.NET Core project that builds and starts with the documented commands (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT)
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

### Input Schema
- `env`: Encrypted environment variables (bucket credentials, secrets)
- `name`: App name (must match `^[a-z0-9-]+$`)
- `path`: Project directory or ample.toml service
- `release_command`: Migration command run before activation

### 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. 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.
5. **Verify**: Fetch the live URL and check the self-test route(s).

### Success Checks
- App responds on its public URL
- Bulk-import-staging self-test

### Examples
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose bulk import staging module was checked live.

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

### Cost Estimate
- Monthly Amount: $10.00 
- Components: App server, Managed PostgreSQL database

### Evidence Summary
- ASP.NET Core pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.