Host documentation site with Astro: bulk content imports · Ample Computer
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). The documentation site-specific behavior (your import format, mapping and conflict rules) is your application code on that verified basis.
Verified: November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
An Astro project that builds and starts with the documented commands (
astro buildwith the@astrojs/nodestandalone adapter thennode ./dist/server/entry.mjson the node-22 template)A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with
--env)A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variablesAn Ample account token with servers:write, databases:read, buckets:read
Exact tested configuration
- Build:
npm run build --if-present - Install:
npm install - Runtime:
node - Sizes: 1vcpu-1gb
- Start:
npm run start - Template: node-22
Steps
Build and start. astro build with the
@astrojs/nodestandalone adapter thennode ./dist/server/entry.mjson the node-22 template. The server must bind 0.0.0.0 on PORT.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.Wire object storage. Create the bucket(s), then pass endpoint, region, bucket and keys as
--envvalues. Use path-style addressing. Keep private data in an unpublished bucket.Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ 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=...
- 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 <deployment_id> --kind buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
- ✓ app responds on its public URL ·
http get/→ “ample canary astro patterns” - ✓ bulk-import-staging self-test ·
http get/p/bulk-import-staging→ “imported=2 rejected=1 restart=ok”
Evidence
November 6, 2026 · canary run
Astro pattern fixture deployed on Ample (astro build with the@astrojs/nodestandalone adapter thennode ./dist/server/entry.mjson the node-22 template); 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).November 5, 2026 · canary run
The same Astro app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested examples
- Astro pattern fixture. Multi-pattern Astro app whose bulk import staging module was checked live; the module is under
tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the documentation site itself (your import format, mapping and conflict rules) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.