page:recipes:documentation site:astro:content imports

Host documentation site with Astro: bulk content imports

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

Representative Queries

• Host documentation site with Astro: bulk content imports
• Where can I host Documentation site built with Astro?
• I need a staged import format, validation procedure and import recovery workflow.

Resource Requirements

• Compute
• Postgres
• S3-compatible object storage

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Postgres: 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: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Prerequisites

1. A Astro project that builds and starts with the documented commands.
2. A PostgreSQL driver reading DATABASE_URL at runtime.
3. A bucket from ample bucket create with credentials as encrypted S3_* environment variables.
4. An Ample account token with appropriate permissions.

Workflow Steps

1. Build and start: astro build then node ./dist/server/entry.mjs on the node-22 template.
2. Implement the pattern on PostgreSQL: Copy the approach into your schema; keep migrations idempotent.
3. Wire object storage: Create bucket(s) and use path-style addressing.
4. Deploy: Run the synchronous deploy.
5. Verify: Fetch the live URL and perform checks.

Limitations

• Verified on the node-22 template.
• Application-specific checks were not separately tested.
• Various S3 operations are not verified.

Cost Estimate

• Monthly Amount: $10.00
• Breakdown:
  • App server (s-1vcpu-1gb): $5.00
  • Managed PostgreSQL database (s-1vcpu-1gb): $5.00

Evidence Summary

• Canary Run: Astro pattern fixture deployed on Ample; checks passed for bulk-import-staging.
• Last Verified: 2026-09-20

Next Actions

• Browse the catalog index.
• Search published recipes by intent, stack, and constraints.