Migrate Render web service: Laravel · Ample Computer
Migration guide
Migrate Render web service: Laravel
Move Laravel compute from Render web service 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 and secret files from the Render dashboard into an env file kept out of the repository. Move separately: Render cron jobs become ample job schedules, disks become Ample volumes, and private services connect with --link. Cutover: Add the custom domain with ample domain add, update DNS from the Render target, keep the Render service until verified, then suspend it. 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
Compute verified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgres verified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
You need
- Authorized access to the Render web service source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read
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
Inventory the source. List what Render web service provides beyond the component you are moving. Plan these separately: Render cron jobs become
ample jobschedules, disks become Ample volumes, and private services connect with--link.Source step 1. Copy environment variables and secret files from the Render dashboard into an env file kept out of the repository.
Source step 2. Translate the Render build and start commands (or
render.yaml) into the repository's manifest or--build-command/--start.Source step 3. Note Render-only features in use: background workers, cron jobs, disks, private services.
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
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).
Cut over. Add the custom domain with
ample domain add, update DNS from the Render target, keep the Render service until verified, then suspend it.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
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 Render web service uses the vendor's standard tooling.
Tested examples
- Laravel pattern fixture (destination). Verified destination basis: Laravel compute.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Render web service's standard tooling.
- Plan separately: Render cron jobs become
ample jobschedules, disks become Ample volumes, and private services connect with--link. - Verified on the php-8.5 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with pg_dump and pg_restore.