Deliver public assets through CDN for Laravel · Ample Computer

Deliver public assets through CDN for Laravel

Cdn assets for a Laravel app on Ample. Verified on Laravel: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. 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.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

install composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

runtime php

sizes - 1vcpu-1gb

start frankenphp php-server --listen :$PORT --root public

template php-8.5

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. Publish a bucket for public assets. Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.

   $ ample bucket publish <bucket-name>
  1. Verify. Fetch the live URL and /p/versioned-static-assets on the example; on failure read the build and runtime logs.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary laravel patterns”
✓ versioned-static-assets check from the example · http get/p/versioned-static-assets → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run

Laravel pattern fixture deployed on Ample (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); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

Tested examples

What it doesn’t cover