# Host documentation site with Astro: object-stored public media

Deploy a documentation site built with Astro on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on Astro: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.

## Summary
Not separately tested: your media processing, object layout and cache policy; treat the documentation site-specific behavior as your application code.

## Representative Queries
- Host documentation site with Astro: object-stored public media
- Where can I host Documentation site built with Astro?
- I need an object layout, public asset URL policy and CDN delivery configuration.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
- primitive:cdn

## 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.
- **CDN**: The CDN host serves objects from published buckets.

## Framework
Astro

## Workload
Documentation site

## 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 PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
- An Ample account token with servers:write, databases:read, 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.
2. **Implement the pattern on PostgreSQL**: 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.
4. **Deploy**: Run the synchronous deploy once and read the result.
5. **Verify**: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

## Examples
- **Astro pattern fixture**: Multi-pattern Astro app whose public media library module was checked live.

## Success Checks
- App responds on its public URL
- Public-media-library self-test

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture.
- The documentation site itself is application code and was not separately tested.

## Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Basis: size prices from pricing.toml
- Components:
  - App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
- Note: Always-on monthly price of the tested sizes.

## Evidence Summary
- Astro pattern fixture deployed on Ample.

## Last Verified At
2026-09-20T03:31:44Z

## Unknowns
- Region availability is unknown until a verified region fact is recorded.