page:recipes:marketplace:nuxt:download delivery
Host marketplace with Nuxt: authorized file delivery
Deploy a marketplace built with Nuxt on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the marketplace-specific behavior as your application code.
Representative Queries
- Host marketplace with Nuxt: authorized file delivery
- Where can I host Marketplace built with Nuxt?
- I need a file entitlement model and an application-enforced download authorization flow.
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.
More Info - 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.
More Info - S3-compatible object storage
Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
More Info
Workflow Steps
- Build and Start
nuxt buildthennode .output/server/index.mjs(reads HOST and PORT) on the node-22 template. The server must bind 0.0.0.0 on PORT. - Implement the Pattern on PostgreSQL
The fixture's module implements generated downloads: an export query rendered to a CSV artifact. 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 --env values. Use path-style addressing. - Deploy
Run the synchronous deploy once and read the result.
Command:ample deploy . --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) from the example; then run your own checks.
Command:ample logs --kind build
Examples
- Nuxt pattern fixture
Multi-pattern Nuxt app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
Source:tests/deploy-canaries/nuxt-patterns
Success Checks
- App responds on its public URL.
Expect:ample canary nuxt patterns - Generated-downloads self-test.
Expect:export=ok rows=3 (with ?token=...; 401 without)
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 marketplace itself (your export formats, retention policy and entitlement model) is application code and was not separately tested.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Basis: Size prices from pricing.toml (loaded by the API)
- App server: s-1vcpu-1gb, Monthly Amount: 5.0
- Managed PostgreSQL database: s-1vcpu-1gb, Monthly Amount: 5.0
Next Actions
Browse the catalog index
- Action ID:
browse-catalog - Method:
GET - Relative Path:
/v1/catalog
- Action ID:
Search published recipes
- Action ID:
search-recipes - Method:
POST - Relative Path:
/v1/catalog/search - Body:
{ "limit": 5, "query": "Host marketplace with Nuxt: authorized file delivery" }
- Action ID:
Prepare a deployment plan
- Action ID:
plan:page:recipes:marketplace:nuxt:download-delivery - Method:
POST - Relative Path:
/v1/catalog/plan - Body:
{ "inputs": {}, "projectId": "", "recipeId": "page:recipes:marketplace:nuxt:download-delivery", "recipeRevision": "r1" }
- Action ID:
Read existing authentication setup
- Action ID:
auth-setup - Method:
GET - Relative Path:
/mcp/setup
- Action ID:
Browse Marketplace
- Action ID:
browse:workload:marketplace - Method:
GET - Relative Path:
/v1/catalog/nodes/workload%3Amarketplace
- Action ID: