Migrate Vercel app: Laravel · Ample Computer

Migrate Vercel app: Laravel

Move Laravel compute from Vercel app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Copy environment variables from the Vercel project settings (or vercel env pull) into an env file you keep out of the repository. Move separately: edge middleware, ISR revalidation and image optimization run in the app or its framework; cron jobs become ample job schedules; reconnect Vercel integrations to the app directly. Cutover: Add the custom domain with ample domain add, set the documented DNS records, keep the Vercel deployment until traffic is verified, then remove the domain from Vercel. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

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. Inventory the source. List what Vercel app provides beyond the component you are moving. Plan these separately: edge middleware, ISR revalidation and image optimization run in the app or its framework; cron jobs become ample job schedules; reconnect Vercel integrations to the app directly.

  2. Source step 1. Copy environment variables from the Vercel project settings (or vercel env pull) into an env file you keep out of the repository.

  3. Source step 2. Note the framework preset, build command and output directory; Ample detects the same from the repository.

  4. Source step 3. List Vercel-only features in use: edge middleware, ISR revalidation, image optimization, cron jobs, integrations.

  5. Deploy on Ample in parallel. 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. Pass the exported variables with --env; keep the source running.

   $ ample deploy . --name <app-name> --public --env-file .env.production
  1. Validate before cutover. Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).

  2. Cut over. Add the custom domain with ample domain add, set the documented DNS records, keep the Vercel deployment until traffic is verified, then remove the domain from Vercel.

  3. Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

How it was checked

✓ destination app responds on its public URL· http get/ → “ample canary laravel patterns”
✓ configuration-secrets check from the destination example· http get/p/configuration-secrets → “see the pattern fixture checks”
✓ relational-records check from the destination example· http get/p/relational-records → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

Evidence

  1. November 6, 2026 · canary run
    Destination side verified: the 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) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Vercel app uses the vendor's standard tooling.

Tested examples

What it doesn’t cover