CorefinityCorefinityDocs
Open the Control PanelControl Panel
Migrate to Corefinity · 3 of 7

Migrate Laravel

Move a Laravel application from another host with an AI assistant, build the copy, then switch the domain.

On this page

Before you start

  • You have what every migration needs: see Cut over and roll back.
  • You know the application's Laravel and PHP versions.
  • You know which queues your workers listen on. Workers on Corefinity process the default queue, so jobs sent to any other queue wait.

What is particular to Laravel

  • The site is created empty. The files are copied without vendor/.
  • A trial copy leaves queued jobs behind, and the final copy brings them. Failed jobs always travel.
  • .env is written from the old one: the database, Redis, sessions, cache and queue settings point at the new site, and APP_KEY stays yours.
  • The assistant runs composer install, storage:link and optimize. It runs migrations only when the code is newer than the data.
  • It tests /, /login, /up and the health or API routes you name, then checks that no queue is left without a worker.

What you decide

  • Every change to the production environment.
  • How front-end assets are built: copied from the old host, or built on the site with the Node.js version your code needs.
  • What to do about a queue with no worker. Corefinity support can have it worked.

Addresses stored inside your application's own data are yours to change.

Start the move

Give the assistant your own values. It follows the migrate-laravel playbook.

Text
Use the Corefinity MCP prompt "migrate-laravel" with domain: app.example.com,
old_host: ssh [email protected], version: 12.
Follow it step by step and tell me before anything that changes my account.
Was this helpful?
Open in ClaudeOpen in ChatGPT