# Host inventory manager with ASP.NET Core: CSV imports

Deploy a inventory manager 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 inventory manager-specific behavior as your application code.

## Representative Queries
- Host inventory manager with ASP.NET Core: CSV imports
- Where can I host Inventory manager built with ASP.NET Core?
- I need a domain CSV format, row validation, deduplication and an import recovery path.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
### Compute
- **Label**: Compute
- **Status**: verified
- **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

### Postgres
- **Label**: Postgres
- **Status**: verified
- **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

### S3-compatible object storage
- **Label**: S3-compatible object storage
- **Status**: verified
- **Summary**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## 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.
   - Command: `ample deploy . --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`.
   - Command: `ample logs  --kind build`

## Examples
### ASP.NET Core pattern fixture
- **Description**: Multi-pattern ASP.NET Core app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
- **Source Ref**: tests/deploy-canaries/asp-net-core-patterns

## Success Checks
1. **App responds on its public URL**
   - *Kind*: http_get
   - *Path*: /
   - *Expect*: ample canary asp net core patterns

2. **Bulk-import-staging self-test**
   - *Kind*: http_get
   - *Path*: /p/bulk-import-staging
   - *Expect*: imported=2 rejected=1 restart=ok

## 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 inventory manager itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.