Host Blog with Laravel: Public-Site Delivery

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

Representative Queries

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

Resource 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.
• CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Infrastructure Requirements

1. Compute: Verified
2. CDN: Verified

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.
2. Wire Object Storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.
3. Deploy: 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.

Examples

• Laravel Pattern Fixture: Multi-pattern Laravel app whose public web service module was checked live.

Success Checks

• App responds on its public URL
• Versioned-static-assets self-test

Limitations

• Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture.
• The blog itself (your site content and build) is application code and was not separately tested.

Cost Estimate

• Monthly Amount: $5.00 (USD)
• Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Last Verified At

• Date: 2026-09-20T20:36:21Z

Next Actions

• Browse the 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 Blog, Laravel, and Public web service
• Browse Deploy web app.