# Host Campaign Site with Astro: Bulk Content Imports

Deploy a campaign site built with Astro 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 Astro: 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 campaign site-specific behavior as your application code.

## Summary
- **Label:** Host campaign site with Astro: bulk content imports
- **Family:** Workload recipe
- **Framework:** Astro
- **Workload:** Campaign site
- **Release Status:** Published
- **Support Status:** Verified
- **Execution Status:** Ready

## Representative Queries
- Host campaign site with Astro: bulk content imports
- Where can I host Campaign site built with Astro?
- I need a staged import format, validation procedure and import recovery workflow.

## Prerequisites
1. A Astro project that builds and starts with the documented commands (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
4. An Ample account token with servers:write, databases:read, buckets:read

## Workflow Steps
1. **Build and Start**  
   astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template. 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 <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 <app_name> --kind build` then `--kind runtime`.
   Command: `ample logs <app_name> --kind build`

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.0

### Components
1. **App Server**: 
   - Size: s-1vcpu-1gb
   - Quantity: 1.0
   - Monthly Amount: 5.0

2. **Managed PostgreSQL Database**: 
   - Size: s-1vcpu-1gb
   - Quantity: 1.0
   - Monthly Amount: 5.0

### Note
Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Astro major versions are not verified.
- The campaign site itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.