# Host Public Directory with Astro: Public-Site Delivery

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

## Representative Queries
- Host public directory with Astro: public-site delivery
- Where can I host Public directory 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.

## Framework
Astro

## Workload
Public directory

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

## 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**: 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.
   ```
   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.
   ```
   ample logs  --kind build
   ```

## Examples
- **Astro Pattern Fixture**: Multi-pattern Astro app whose public web service module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## 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 public directory 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
- **Basis**: size prices from pricing.toml at build revision.
- **Components**: App server (s-1vcpu-1gb) - Quantity: 1.0, Monthly Amount: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Next Actions
1. **Browse the Catalog**: Browse the catalog index 
   - Method: GET
   - Path: /v1/catalog

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

3. **Plan Deployment**: Prepare a side-effect-free deployment plan for an authorized project 
   - Method: POST
   - Path: /v1/catalog/plan

4. **Read Existing Auth Setup**: Read the existing agent authentication setup 
   - Method: GET
   - Path: /mcp/setup

5. **Browse Public Directory**: Browse Public directory 
   - Method: GET
   - Path: /v1/catalog/nodes/workload%3Apublic-directory

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

7. **Browse Public Web Service**: Browse Public web service 
   - Method: GET
   - Path: /v1/catalog/nodes/pattern%3Apublic-web-service

8. **Browse Deploy Web App**: Browse Deploy web app 
   - Method: GET
   - Path: /v1/catalog/nodes/intent%3Adeploy-web-app
