# Host company website with Astro: public-site delivery

## Summary
Deploy a company website 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.

## Representative Queries
- Host company website with Astro: public-site delivery
- Where can I host Company website 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**  
   - 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.

2. **CDN**  
   - Status: verified  
   - Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## Framework
- **Astro**

## Workload
- **Company website**

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

## Tested Configuration
- **Template**: node-22
- **Runtime**: node
- **Size**: s-1vcpu-1gb
- **Install**: npm install
- **Build**: npm run build --if-present
- **Start**: npm run start

## Workflow Steps
1. **Build and start**  
   - **Body**: 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**  
   - **Body**: 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**  
   - **Body**: 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.  
   - **Command**: 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**  
   - **Body**: 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`.  
   - **Command**: ample logs  --kind build

## Success Checks
- **App responds on its public URL** 
  - **Kind**: http_get  
  - **Path**: /  
  - **Expect**: ample canary astro patterns

- **Versioned-static-assets self-test** 
  - **Kind**: http_get  
  - **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 company website itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Evidence Summary
1. **Canary run**  
   - **Summary**: Astro pattern fixture deployed on Ample; checks passed for versioned-static-assets and configuration-secrets. 
   - **Observed At**: 2026-09-20T03:31:44Z

2. **Canary run**  
   - **Summary**: The same Astro app deployed with a --release-command migration; the marker it created was readable after activation.
   - **Observed At**: 2026-09-20T01:54:51Z

## Formats
- **HTML**: [https://ample.computer/recipes/company-website/astro/public-site](/content/recipes/company-website/astro/public-site/index.html)
- **Markdown**: [https://ample.computer/recipes/company-website/astro/public-site.md](/content/recipes/company-website/astro/public-site.md)
- **JSON**: [https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Acompany-website%3Aastro%3Apublic-site](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Acompany-website%3Aastro%3Apublic-site)

## Next Actions 
1. **Browse the catalog index**  
   - **Operation ID**: catalog_index  
   - **Method**: GET  
   - **Relative Path**: /v1/catalog

2. **Search published recipes by intent, stack and constraints**  
   - **Operation ID**: search_recipes  
   - **Method**: POST  
   - **Relative Path**: /v1/catalog/search

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - **Operation ID**: plan_deployment  
   - **Method**: POST  
   - **Relative Path**: /v1/catalog/plan

4. **Read the existing agent authentication setup**  
   - **Operation ID**: existing_auth_setup  
   - **Method**: GET  
   - **Relative Path**: /mcp/setup

5. **Browse Company website**  
   - **Operation ID**: browse_node  
   - **Method**: GET  
   - **Relative Path**: /v1/catalog/nodes/workload%3Acompany-website

6. **Browse Astro**  
   - **Operation ID**: browse_node  
   - **Method**: GET  
   - **Relative Path**: /v1/catalog/nodes/stack%3Aframework-astro

7. **Browse Public web service**  
   - **Operation ID**: browse_node  
   - **Method**: GET  
   - **Relative Path**: /v1/catalog/nodes/pattern%3Apublic-web-service

8. **Browse Deploy web app**  
   - **Operation ID**: browse_node  
   - **Method**: GET  
   - **Relative Path**: /v1/catalog/nodes/intent%3Adeploy-web-app