# 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.

## Summary
Source procedure: Copy environment variables from the Vercel project settings (or `vercel env pull`) into an env file you keep out of the repository. Not migrated automatically: Edge middleware, ISR revalidation, image optimization, cron jobs and Vercel integrations are not migrated and are unverified on Ample.

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.

## Representative Queries
- Migrate Vercel app: Laravel
- Where can I host Laravel built with Laravel?
- I need a component-scoped export/import or reconfiguration procedure for Laravel, with compatibility checks, verification and rollback.

## Workflow Steps
1. **Inventory the source**  
   List what Vercel app provides beyond the component you are moving. Out of scope here: Edge middleware, ISR revalidation, image optimization, cron jobs and Vercel integrations are not migrated and are unverified on Ample.

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.
   
   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; 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`, set the documented DNS records, keep the Vercel deployment until traffic is verified, then remove the domain from Vercel.

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
- **Laravel pattern fixture (destination)**  
   Verified destination basis: Laravel compute.  
   Source Reference: `tests/deploy-canaries/laravel-patterns`

## Success Checks
- **HTTP GET** check at `/` expects "ample canary laravel patterns".
- **HTTP GET** check at `/p/configuration-secrets` expects "see the pattern fixture checks".
- **HTTP GET** check at `/p/relational-records` expects "see the pattern fixture checks".
- **Manual** check for data or object counts and checksums to match the source; expects operator comparison before cutover.

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from Vercel app's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
  
#### Components
- **App Server**  
   Size: s-1vcpu-1gb  
   Quantity: 1.0  
   Monthly Amount: 5.0
  
- **Managed PostgreSQL Database**  
   Size: s-1vcpu-1gb  
   Quantity: 1.0  
   Monthly Amount: 5.0
   
*Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.*

## Evidence Summary
- **Canary Run**: Destination side verified: the Laravel pattern fixture deployed on Ample. The export from Vercel app is documented from the vendor's standard tooling and was not executed by this catalog's evidence. Observed at 2026-09-20T20:36:21Z.

## Next Actions
1. **Browse the catalog index**  
   Action ID: `browse-catalog`, Operation ID: `catalog_index`, Method: `GET`, Path: `/v1/catalog`.

2. **Search published recipes by intent, stack and constraints**  
   Action ID: `search-recipes`, Operation ID: `search_recipes`, Method: `POST`, Path: `/v1/catalog/search`.