page:recipes:company website:laravel:public site

Host Company Website with Laravel: Public-Site Delivery

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


Representative Queries


Resource Requirements

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.
    Learn more.
  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.
    Learn more.

Framework

Workload

Release Status

Support Status

Execution Status


Prerequisites


Tested Configuration


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


Limitations


Cost Estimate

The tested sizes are allocated priced per quota and are not included.