Host company website with Astro: bulk content imports

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

Representative Queries

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

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

Compute

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

Postgres

• Label: Postgres
• 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.
• Status: verified

S3-compatible Object Storage

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

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 --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

Astro Pattern Fixture

• Description: Multi-pattern Astro app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
• Source Ref: tests/deploy-canaries/astro-patterns

Success Checks

• App responds on its public URL: Kind: http_get, Path: /, Expect: ample canary astro patterns.
• Bulk-import-staging self-test: Kind: http_get, Path: /p/bulk-import-staging, Expect: imported=2 rejected=1 restart=ok.

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 company website 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

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  • 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.

Evidence Summary

• Canary Run: Astro pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets. Pattern proof: 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).
• Last Verified At: 2026-09-20T03:31:44Z

Next Actions

• Browse the catalog index: Relative Path: /v1/catalog
• Search published recipes by intent, stack and constraints: Relative Path: /v1/catalog/search, Body: {"limit":5,"query":"Host company website with Astro: bulk content imports"}
• Prepare a side-effect-free deployment plan for an authorized project: Relative Path: /v1/catalog/plan, Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:company-website:astro:content-imports","recipeRevision":"r1"}