page:recipes:blog:astro:public site

Host blog with Astro: public-site delivery

Deploy a blog built with Astro on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Astro: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the blog-specific behavior as your application code.

Representative Queries

• Host blog with Astro: public-site delivery
• Where can I host Blog built with Astro?
• I need an explicit origin-to-CDN delivery path and a tested public content build.

Resource Requirements

• Compute
• CDN

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Prerequisites

• A Astro project that builds and starts with the documented commands (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, buckets:read

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. 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. Publish only the bucket that serves public assets and reference its CDN URL.
3. 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=... --env CDN_PUBLIC_URL=...
   

4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) 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
  • Path: /
  • Expect: ample canary astro patterns
• versioned-static-assets self-test
  • Path: /p/versioned-static-assets
  • Expect: a CDN URL whose content is served publicly

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 blog itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • app server: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 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 versioned-static-assets and configuration-secrets.
  • Observed At: 2026-09-20T03:31:44Z
  • Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
• Canary Run: Same Astro app deployed with a --release-command migration.
  • Observed At: 2026-09-20T01:54:51Z
  • Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)

Next Actions

1. Browse the catalog index: GET /v1/catalog
2. Search recipes: POST /v1/catalog/search with query "Host blog with Astro: public-site delivery"
3. Prepare a deployment plan: POST /v1/catalog/plan with the specified recipeId
4. Read the existing agent authentication setup: GET /mcp/setup
5. Browse Blog: GET /v1/catalog/nodes/workload%3Ablog
6. Browse Astro: GET /v1/catalog/nodes/stack%3Aframework-astro
7. Browse Public web service: GET /v1/catalog/nodes/pattern%3Apublic-web-service
8. Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app