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
- Compute
- Postgres
Infrastructure 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.
- Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
Workflow Steps
- 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-commandfor release tasks.
- 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
- Source step 1
- Export config vars with
heroku config -s -ainto an env file kept out of the repository.
- Export config vars with
- Source step 2
- Translate the
Procfileweb process into the start command (--startor the package manifest's start script); worker processes need a separate--kind workerservice.
- Translate the
- Source step 3
- Note buildpacks and add-ons in use; managed databases replace Heroku Postgres, other add-ons need their own plan.
- Deploy on Ample in parallel
composer install --no-devfrom 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
- 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).
- 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.
- Add the custom domain with
- Rollback
- Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.
Examples
- Laravel pattern fixture (destination): Verified destination basis: Laravel compute.
- Source Ref:
tests/deploy-canaries/laravel-patterns
- Source Ref:
Success Checks
- Destination app responds on its public URL
- Kind: http_get
- Path:
/ - Expect:
ample canary laravel patterns
- Configuration-secrets check from the destination example
- Kind: http_get
- Path:
/p/configuration-secrets - Expect:
see the pattern fixture checks
- Relational-records check from the destination example
- Kind: http_get
- Path:
/p/relational-records - Expect:
see the pattern fixture checks
- Data or object counts and checksums match the source
- Kind: manual
- Expect:
operator comparison before cutover
Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- Source-side procedure is documented from Heroku app's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- No full source-product parity is claimed: Heroku add-ons other than Postgres, release-phase scheduling, dyno autoscaling and Heroku Scheduler are not migrated; use
--release-commandfor release tasks.
Cost Estimate
- Monthly Amount: $10.00 (USD)
- Components:
- App server: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
- Managed PostgreSQL database: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
- Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.
- Components: