Host knowledge base with Nuxt: bulk content imports

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

Representative Queries

• Host knowledge base with Nuxt: bulk content imports
• Where can I host Knowledge base 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

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 Nuxt project that builds and starts with the documented commands (nuxt build then node .output/server/index.mjs (reads HOST and PORT) 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

Input Schema

• env: Encrypted environment variables (bucket credentials, secrets)
• name: App name
• path: Project directory or ample.toml service
• release_command: Migration command run before activation

Required Properties

• env
• name
• path

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

Examples

Nuxt pattern fixture

Multi-pattern Nuxt app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

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 knowledge base itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Monthly Amount: $10.00 USD (authoritative) based on the size prices from pricing.toml. Components:
  • App server: s-1vcpu-1gb
  • Managed PostgreSQL database: s-1vcpu-1gb
  • Note: Always-on monthly price for tested sizes; buckets are allocation-priced per quota and not included.

Evidence Summary

• Canary run of the Nuxt pattern fixture deployed on Ample with checks passing for bulk-import-staging and configuration-secrets.

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Knowledge base
• Browse Nuxt
• Browse Bulk import staging
• Browse Deploy web app