page:migrate:heroku app:laravel

Migrate Heroku app: Laravel

Move Laravel compute from Heroku 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

Export config vars with heroku config -s -a into an env file kept out of the repository. Not migrated automatically: Heroku add-ons other than Postgres, release-phase scheduling, dyno autoscaling and Heroku Scheduler are not migrated; use --release-command for release tasks.

Cutover

Add the custom domain with ample domain add, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down.

Rollback

Keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Resource Requirements

Infrastructure Requirements

Workflow Steps

  1. Inventory the source
    • List what Heroku app provides beyond the component you are moving. Out of scope here: Heroku add-ons other than Postgres, release-phase scheduling, dyno autoscaling and Heroku Scheduler are not migrated; use --release-command for release tasks.
  2. Source step 1
    • Export config vars with heroku config -s -a into an env file kept out of the repository.
  3. Source step 2
    • Translate the Procfile web process into the start command (--start or the package manifest's start script); worker processes need a separate --kind worker service.
  4. Source step 3
    • Note buildpacks and add-ons in use; managed databases replace Heroku Postgres, other add-ons need their own plan.
  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.
    • Command: ample deploy . --name --public --env-file .env.production
  6. Validate before cutover
    • Run the app's own checks and, for data, compare counts and checksums; example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).
  7. Cut over
    • Add the custom domain with ample domain add, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down.
  8. Rollback
    • Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

Examples

Success Checks

Limitations

Cost Estimate