Migrate Railway app: Laravel · Ample Computer

Migrate Railway app: Laravel

Move Laravel compute from Railway 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 variables from the Railway service (Variables tab or railway variables) into an env file kept out of the repository. Move separately: Railway cron schedules become ample job schedules, volumes become Ample volumes, and private services connect with --link. Cutover: Add the custom domain with ample domain add, update DNS from the Railway target, keep the Railway service until verified, then remove it. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

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 Railway app provides beyond the component you are moving. Plan these separately: Railway cron schedules become ample job schedules, volumes become Ample volumes, and private services connect with --link.

  2. Source step 1. Export variables from the Railway service (Variables tab or railway variables) into an env file kept out of the repository.

  3. Source step 2. Translate railway.json/Nixpacks settings into the repository's build and start commands; Ample detects Node and Python builds itself.

  4. Source step 3. Note Railway-only features in use: cron schedules, volumes, private networking, templates.

  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
    ```

6. **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).

7. **Cut over.** Add the custom domain with `ample domain add`, update DNS from the Railway target, keep the Railway service until verified, then remove it.

8. **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 Railway app 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 database` or `ample bucket` command you run.
- The destination side was verified on Ample with the pattern fixture; the source-side steps use Railway app's standard tooling.
- Plan separately: Railway cron schedules become `ample job` schedules, volumes 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.