Host knowledge base with Laravel: public-site delivery

Deploy a knowledge base built with Laravel 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 Laravel: 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 knowledge base-specific behavior as your application code.

Representative Queries

• Host knowledge base with Laravel: public-site delivery
• Where can I host Knowledge base built with Laravel?
• I need an explicit origin-to-CDN delivery path and a tested public content build.

Resource Requirements

• primitive:compute
• primitive:cdn

Infrastructure Requirements

• 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.
  More info
• 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.
  More info

Prerequisites

• A Laravel project that builds and starts with the documented commands (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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: php-8.5
• Runtime: php
• Size: s-1vcpu-1gb
• Install Command: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• Start Command: frankenphp php-server --listen :$PORT --root public

Workflow Steps

1. Build and start
   • composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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.
   • 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
   • 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 laravel 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 php-8.5 template at s-1vcpu-1gb with the example fixture; other sizes, templates, and Laravel major versions are not verified.
• The knowledge base 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.
  • Components:
    • App server: s-1vcpu-1gb, Quantity: 1, Monthly Amount: 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.

Next Actions

• Browse catalog index
• Search published recipes by intent, stack, and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Knowledge base
• Browse Laravel
• Browse Public web service
• Browse Deploy web app

For more information, refer to HTML version
or Markdown version.