Host documentation site with Nuxt: bulk content imports

Deploy a documentation site built with Nuxt 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 Nuxt: 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 Nuxt: bulk content imports
• Where can I host Documentation site built with Nuxt?
• 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

• 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

• 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

• 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
   nuxt build then node .output/server/index.mjs (reads HOST and PORT) 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.
   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) (/api/p/bulk-import-staging) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   ample logs --kind build

Success Checks

• app responds on its public URL
• bulk-import-staging self-test

Limitations

• Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Nuxt major versions are not verified.
• The documentation site itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

Cost Estimate

Monthly Amount: $10.00
Summary: Apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.