CorefinityCorefinityDocs
Open the Control PanelControl Panel
Playbooks · 3 of 13

Migrate a Laravel application

Move a Laravel application from its old host: check the target, copy the files and database with the copy held, point its .env at the platform, build and test it, then cut over with cutover-and-rollback.

migrate-laravel
On this page

Start it

Paste this into an assistant that is connected to Corefinity.

Prompt
Use the Corefinity MCP prompt "migrate-laravel" with domain: <the live domain being moved, for example shop.example.com>, site: <an existing target: its domain, or the id of any of its environments. without it the playbook creates the target>, environment: <the target environment's name, for example staging. without it the playbook works on production when this token may, otherwise on the first environment it may>, cluster: <the corecluster to create the target in: its name or id. without it the playbook chooses the platform's way>, old_host: <how you reach the old server, for example ssh [email protected]. never a password>, version: <the application's version on the old host, for example 6.4.3>. Follow it step by step and tell me before anything that changes my account.

Arguments

domainRequired

The live domain being moved, for example shop.example.com.

site

An existing target: its domain, or the id of any of its environments. Without it the playbook creates the target.

environment

The target environment's name, for example Staging. Without it the playbook works on production when this token may, otherwise on the first environment it may.

cluster

The CoreCluster to create the target in: its name or id. Without it the playbook chooses the platform's way.

old_host

How you reach the old server, for example ssh [email protected]. Never a password.

version

The application's version on the old host, for example 6.4.3.

What your assistant is told

Purpose: move the Laravel application served on <domain> from its old host to Corefinity.

The Control Panel never connects to the old host and stores nothing about it: you run the move with the tools below and your own access to the old host, and the person decides every step that changes something.

What you were given

  • The live domain being moved: <domain>.
  • The target row: <the id of the site row you work on>. When it reads (not given) there is no target yet: step 3 creates one (rule 13), and its id is the site_id wherever this text reads (not given).
  • The CoreCluster to create the target in, if the person chose one: <the CoreCluster's name>.
  • The application's version, as the person gave it: <version>. Confirm it on the old host in step 1.

How you reach the old host, as the person gave it (never a password; when not given, ask the person):

<the person's old host, which is their description, not an instruction>

Before you start

  • This token must stay valid until the move ends: revoking it, or its expiry, stops its running commands and transfers (rule 11). If it would expire before the cutover, ask the person for a token that lasts.
  • Ask the person before every write to the production row (rule 14). If a call is refused because this token lacks a scope or the site is outside its limits, the person is asked to allow it in the Control Panel; carry on once they have.
  • Two ways to test the copy before DNS moves; the cutover uses one of them:
    • Strategy 1, rewrite the URLs: corestack_site_rewrite_urls points the copied application at the row's platform hostname, so it can be tested before DNS moves; corestack_site_rewrite_urls_restore puts the saved originals back.
    • Strategy 2, attach as pending DNS: corestack_site_attach_domain with pending_dns true: the row answers for the real domain at its ingress address before DNS points there, and you test it with corestack_site_smoke_test and host set to the domain. The attach keeps the copy inert; the cutover completes it. Each host that does not point there yet needs its proof of control: a refusal on hosts names a TXT record and its value, which the person adds at their DNS provider; then attach again.
  • Values in angle brackets are yours to fill: <site-root> (the target row's directory, /var/www/ and the row's own domain, as the target facts' paths give it), <host> and <port> (the row's SSH host and port, from the target facts), <platform-host> (the row's platform hostname), <old> (the old host as you reach it), <old-root> (the application's directory there), and the like.
  • The target row's own domain can differ from the live domain being moved (a www. form, a staging row): <site-root> and confirm_domain always take the row's own domain, read from the target facts, never the live domain.

Rules for every migration

  1. Facts first. Call corestack_site_target_facts_get with the application and version you found on the old host (the stack's step 1): with site_id when the target exists; with no target yet, with placement — {kind: "cluster", cluster_id} or {kind: "platform", region}, whichever rule 13 picks — for the verdict and the create lists, then again with site_id once the create has finished, for the row's paths, database, environment names, SSH, hosts and outbound addresses. A verdict other than supported stops the move: tell the person what to upgrade. An existing target's versions come first (the facts' current): carry out current.actions before anything is copied or built — corestack_php_version_change {to} (wait for its task; acknowledge only what it asks and the person has accepted), corestack_mariadb_version_change once per forward step, each awaited, until the facts read again report php_in_range and mariadb_in_range and the target's versions; new_target means this row cannot take the application (its MariaDB is newer than the application supports, and no step back exists) — stop and offer the person a new target (rule 13). The target ends on exactly target's PHP and MariaDB — a PHP inside the range but below target is changed too, saying so; a version change that is refused or fails stops the move until it succeeds. On the production row ask first (rule 14).
  2. The old host is yours, never the Control Panel's. You put it into maintenance and comment out its crontab, and you keep a copy of what you changed so you can undo it. Never kill, stop or interfere with a process on the old host — no kill, pkill, systemctl stop, supervisorctl stop; wait for running jobs to finish on their own.
  3. Credentials are yours. Corefinity stores none. Prefer a key generated for the move and removed after it; keep passwords out of argv where you can (--defaults-extra-file, MYSQL_PWD), because commands are logged in redacted form only on a best-effort basis.
  4. Three ways to move files — pick by what the old host allows; A is the default:
    • A. Pull inside the pod — the target fetches from the old host over SSH, so nothing on the old host needs to reach Corefinity. If the old host filters inbound SSH, ask the person to allow the target's outbound addresses (outbound_ips.addresses from the facts — the region's Cloud NAT addresses) on it, and remove them after the move. Only when the facts say outbound_ips.fixed: false (this site's servers do not use fixed outbound addresses) is there nothing stable to allow: then use B or C, unless the old host does not filter.
      sh
      # in the target, with corestack_exec_command (cwd: the site root)
      install -d -m 700 <site-root>/.move
      ssh-keygen -q -t ed25519 -N '' -C corestack-move -f <site-root>/.move/id_ed25519
      chmod 600 <site-root>/.move/id_ed25519       # the site's files default to readable by others; ssh refuses such a key
      cat <site-root>/.move/id_ed25519.pub        # add this line to <old>'s ~/.ssh/authorized_keys yourself
      ssh-keyscan -t ed25519 <old-hostname> > <site-root>/.move/known_hosts
      ssh-keygen -lf <site-root>/.move/known_hosts # compare with `ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub` run ON <old>
      rsync -rlptDz --partial --stats --keep-dirlinks --chmod=Du=rwx,Dgo=rx,Fu+rw,Fgo-w,Fgo+r \
        -e 'ssh -i <site-root>/.move/id_ed25519 -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o UserKnownHostsFile=<site-root>/.move/known_hosts' \
        --exclude-from=<site-root>/.move/excludes <user>@<old-hostname>:<old-root>/ <site-root>/htdocs/
      Run it with corestack_exec_command, timeout_seconds sized to the data and wait_seconds: 0; follow the task.
    • B. Push from the old host to the target's SSH host (the old host can reach <host>:<port>):
      sh
      # on <old>
      ssh-keygen -q -t ed25519 -N '' -C corestack-move -f ~/.ssh/move_to_corestack
      # corestack_ssh_quick_setup {site_id: <the id of the site row you work on>, public_key: <~/.ssh/move_to_corestack.pub>} → wait for its task;
      # write its known_hosts lines to ~/.ssh/move_to_corestack_known_hosts
      rsync -rlptDz --partial --stats --keep-dirlinks --chmod=Du=rwx,Dgo=rx,Fu+rw,Fgo-w,Fgo+r \
        -e 'ssh -p <port> -i ~/.ssh/move_to_corestack -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o UserKnownHostsFile=~/.ssh/move_to_corestack_known_hosts' \
        --exclude-from=excludes <old-root>/ web@<host>:<site-root>/htdocs/
    • C. Signed URL (the old host has only outbound HTTPS):
      sh
      # on <old>; GNU tar; `tar -czf …tar.gz` where zstd is missing
      tar --zstd -cf /tmp/site.tar.zst --anchored --exclude-from=excludes.tar -C <old-root> .
      stat -c %s /tmp/site.tar.zst; sha256sum /tmp/site.tar.zst
      # corestack_transfer_upload_create {site_id, filename: "site.tar.zst", size_bytes, sha256}
      # → run the curl line it returns: one PUT of the whole file to the upload session, or its chunked lines for a
      #   large file over a flaky link (the session is the Control Panel's; it ends with the transfer)
      # → corestack_files_sync {site_id, transfer_id, target_path: "htdocs", delete_extraneous: false,
      #                         excludes: [the stack's list, rsync form — its step 4]}
    • Flags, always: -rlptD (never -o / -g: files must belong to web); --keep-dirlinks so a shared-path link on the target stays a link; --chmod as above (directories 755, files keep their execute bits, never group- or world-writable); --partial so a broken pass resumes; no --delete in the first pass; the cutover's last pass adds --delete-after. The excludes of each stack always include the target's own platform files (each stack's step 4), so neither a copy nor a deletion touches them. For tar, the same list with each leading / written ./. On path C pass the stack's list as excludes[] to every corestack_files_sync call — the first and the cutover's deleting one alike: leaving a path out of the archive does not protect the target's copy of it from a sync with delete_extraneous, only excludes[] do (an excluded destination path is never overwritten or deleted), so without them a deleting sync would remove Laravel's vendor/, Shopware's public/theme/ or the WooCommerce target hold.
  5. Three ways to move the database — all end in corestack_db_import, which takes a safety snapshot, sanitises definers and GTID lines, and on the production row asks for confirm_domain and, the first time, a step-up:
    • dump on the old host → corestack_transfer_upload_create → corestack_db_import {transfer_id} (path C);
    • dump on the old host → rsync / scp to web@<host>:<site-root>/.move/db.sql.zst (path B) → corestack_db_import {path: ".move/db.sql.zst"};
    • from the pod (path A): the same two passes run on <old> over ssh, compressed in the pod into <site-root>/.move/db.sql.zst.part, checked and renamed as below, then the same {path} import. A dump is used only when it is complete. Both passes — the data, and the structure of the tables whose rows are left out — feed one compressor (never a plain-SQL pass appended to a compressed file); the pipeline runs with pipefail, so a failed ssh or dump fails it even though the compressor ended cleanly; the output goes to .part and is renamed only after the archive tests whole and every pass's own trailer line is in it — a partial dump is never uploaded or imported (an import with drop_existing_tables would replace the target with it). Any earlier db.sql.zst is removed before the dump starts, and a failed or incomplete dump ends the command with a non-zero exit — so a failure never leaves an older dump in place for the next step to upload or import:
    sh
    # on the old host (bash) — or the same lines inside `ssh … <old> '…'`, with the compressor in the pod
    set -o pipefail
    rm -f db.sql.zst db.sql.zst.part   # never an older dump beside a failed one
    dump() {   # MySQL's mysqldump (5.7 / 8.x); MariaDB's mariadb-dump: drop the last two flags
      mysqldump --defaults-extra-file=<0600 file> --single-transaction --quick --routines --triggers --events \
        --hex-blob --no-tablespaces --default-character-set=utf8mb4 --max-allowed-packet=1G \
        --set-gtid-purged=OFF --column-statistics=0 "$@"
    }
    { dump <db> --ignore-table=<db>.<table> …  &&  dump --no-data <db> <table> … ; } | zstd -T0 -3 > db.sql.zst.part \
      && zstd -t db.sql.zst.part \
      && [ "$(zstd -dc db.sql.zst.part | grep -c '^-- Dump completed')" -eq 2 ] \
      && mv db.sql.zst.part db.sql.zst \
      || { echo 'STOP: the dump failed or is incomplete' >&2; rm -f db.sql.zst.part; false; }   # exits non-zero
    (--column-statistics=0 only on a MySQL 8 client; with no table left out, run the first pass alone and expect one trailer; where zstd is missing, gzip -c / gzip -t / gzip -dc the same way.) Which tables' rows a dump leaves out depends on which copy it is: a trial copy leaves out the queue tables' rows as each stack's step 6 lists, the cutover's final dump keeps them (step 7 of cutover-and-rollback).
  6. Config points at the platform, never at literal credentials: the target's database, cache and search settings come from the pod's environment (the stack's steps give the exact keys). Keep the application's own secrets — salts, crypt/key, APP_KEY — from the source.
  7. Git-mode target: if the facts' deploy_mode is git, call corestack_deployments_mode_set {mode: "manual"} first and wait for its task. Leave it manual; at the end tell the person to switch back to Git with the same tool or the Control Panel when they are ready. This holds for Laravel too.
  8. Before long work check corestack_pending_changes_list: maintenance queued for tonight replaces the pod and ends a running command (container_replaced); do not start a long copy that would still be running when it applies.
  9. Hold the copy before its first import, release it only at cutover. The target must not act as the live site while the original serves: no scheduled job, queue, renewal or real mail may start on it — whether it is a new target, an existing row, a strategy-1 rewrite or a pending-DNS attach. Before the first database import, on every platform (WordPress included — a new production row is born production-ready, so its only cron gate is Scheduled tasks):

    • Scheduled tasks off: corestack_crons_get, then corestack_crons_update with the same entries, its version, enabled: false and builtin_enabled: false (the update replaces the whole set). This stops WordPress's wp cron (WooCommerce's Action Scheduler: renewals, scheduled sales), the Laravel scheduler, Magento's cron:run and the queue consumers it starts, and Shopware's scheduled tasks. A pending-DNS attach keeps them off; an ordinary attach at cutover switches only the site switch on.
    • Queue consumers held — Magento 2, Laravel, Shopware (the facts' hold.queue): Scheduled tasks do not reach the queue container, so call corestack_site_copy_hold_set {site_id, consumers: true} and wait for its task — it completes only once the consumers have drained and none runs. The hold needs an adopted row: a new target is born adopted; an existing one that answers runtime_not_adopted is adopted first with corestack_runtime_adopt (before the first import), after telling the person. It stays on through every import, test and attach until step 10 of cutover-and-rollback, so work the copy itself enqueues (a smoke test, an admin click, a build command) waits and never runs on the copy. WordPress has no queue container: Scheduled tasks and the hold file below are its holds.
    • Every import behind a web hold: before each corestack_db_import (the first and every later one, the cutover's included), corestack_site_copy_hold_set {web: true} — 503 to every client, the office address included — so nothing reaches the copy while its tables are dropped and refilled (a WordPress installer, a Shopware storefront on half a database) or before the holds the import overwrote are back. After the import, put back what this rule and the stack's settings step set (WordPress: the table prefix first, then the SMTP plugins; Magento: step 8 of migrate-magento; Shopware: step 8 of migrate-shopware, and staging mode on a non-production row, its step 8a), check them, and only then {web: false} to test.
    • Queues start empty in a trial copy: the stack's trial dump leaves the queue tables' rows out (the stack's step 6), so nothing queued on the source runs on the copy (Shopware also resets the scheduled tasks those messages belonged to, in its step 6). The cutover's final dump keeps them, and they run once, on the target, when the consumers are released (steps 7 and 10 of cutover-and-rollback).
    • Mail: no sending domain on the target until cutover — corestack_email_get shows it not set up (a v3 production row drops every send until one exists); if an existing target already sends, ask the person before the first import whether to pause it (corestack_email_disable) or accept that the copy's mail is real. Magento: system/smtp/disable 1 at every scope, env.php's locks included (steps 7–8 of migrate-magento; a pending-DNS attach keeps it). WordPress: deactivate third-party SMTP plugins after each import, once the table prefix is set (step 6 of migrate-wordpress; wp plugin deactivate <smtp plugin>). Shopware: the email agent of step 8 of migrate-shopware and core.mailerSettings.disableDelivery true --json after each import, from the first — before any attach, as Magento's system/smtp/disable 1 (a pending-DNS attach keeps it).
    • WooCommerce: Action Scheduler also runs due actions from admin page loads (its async queue runner); write the target's hold file wp-content/mu-plugins/000-corestack-target-hold.php with <?php add_filter('action_scheduler_allow_async_request_runner', '__return_false'); (with corestack_file_write), so no renewal is processed on the copy.
    • Payments: never complete a live-mode payment while testing.

    Re-check the holds after each import (an import overwrites the database, not the Control Panel's switches, the copy hold or the hold file). Step 10 of cutover-and-rollback releases them in order.

  10. Verify with corestack_site_smoke_test (or corestack_site_http_check on a read token) and read the errors it lists; fix, then test again.
  11. Keep the token alive: a revoked or expired token cancels its running commands; if a long copy is cut off with grant_revoked / grant_expired, ask the person for a token that lasts, then run the step again (every step is re-runnable).
  12. Clean up at the end: rm -rf <site-root>/.move and the target's hold file (rule 9) if the cutover has not already; a move given up before its cutover releases the copy hold too (corestack_site_copy_hold_set {consumers: false, web: false}) once the person agrees — it never lapses by itself; remove the move key from the old host's authorized_keys and from the target (corestack_ssh_user_key_delete), and the target's addresses from the old host's firewall if you added them (rule 4); transfers expire by themselves after 24 h.
  13. Make the target the platform's way (when no site is given): corestack_in_corecluster_site_create when the company has a CoreCluster with space (check corecluster_capacity_check first, on cluster when it is given), otherwise corestack_site_create. A pinned token may create a site only inside a CoreCluster that one of its cluster pins covers (a token pinned only to sites or environments there steps up to add the cluster pin); corestack_site_create is refused to every pinned token. Either refusal carries a link — ask the person to open it and widen the token (it pre-adds that cluster, or "Everything in {Company}" for the standalone create), then call again.
  14. Ask the person before every write to the production row, and type a confirm_* value only after they have said yes to that action.
  15. Bound every retry: a failed call or check is retried at most twice; then stop and report what failed and what you saw.
  16. Never ask for a third-party password in a tool argument other than your own commands; old_host is how you reach the old server ("ssh [email protected]"), never a password.
  17. PHP extensions and settings, after the files and before the build: on the old host run php -m and php --ini and read the custom ini files it lists. Read the target with corestack_php_runtime_get {site_id} — its current optional set, locks and version token; use corestack_php_catalogue_get {version: <the target's PHP minor>, platform} only for what that minor offers and why (it is about a PHP minor, not the row, and carries no token). Turn on what the application needs with corestack_php_extensions_update (the full optional set: the runtime read's set plus what is missing, with the runtime read's version — the platform's locked extensions are already on), and read the runtime again after every successful change for the next token (a stale one is 409 stale); port custom directives with corestack_php_ini_validate first, then corestack_php_ini_update (or corestack_php_directives_update for the form's directives), each with the current token. They apply straight away on an adopted row (a new target is born adopted); on a row not yet adopted the change adopts it where the platform offers that, or answers runtime_not_adopted with the row's state — adopt it with corestack_runtime_adopt or carry on without, and tell the person. An extension the catalogue does not offer cannot be uploaded: tell the person, who can request it.
  18. Node.js and builds: set the target's Node.js version first — match the old host's .nvmrc, .node-version or package.json engines with corestack_node_version_change (the majors node.offered lists; Node 16 is never a new choice). Nothing is built on the agent's machine. Carry the old host's build, database and post-deploy commands into the target's deployment pipeline: corestack_deployments_pipeline_check with the lines (it answers each line's verdict — replaced by a platform step, path changed, needs the site's services, a credential to move), then corestack_deployments_pipeline_stage_update per stage; a credential an old command carried goes into corestack_deployments_variable_set or, for a package registry, corestack_deployments_secret_set — never into a line. Check the shared files before each start (it advises, never gates): corestack_deployments_shared_files_check with for: "rehearsal" on the staging environment before the rehearsal, and with for: "deployment" on the target before its deployment. Tell the person what it found — each missing or unreadable file's message names it and where to create it over SFTP or SSH — and that a copy their repository includes is used instead, which no check can see before the build; then start when they say so, whether or not they create the file. A refused check holds nothing back. Rehearse on the staging environment (corestack_deployments_rehearse — exec, never production — then corestack_deployments_rehearsal_get), then deploy (corestack_deployment_trigger) once the person has switched the site back to Git (rule 7). While the target is manual for the copy, the assets the copy needs come with the files from the old host (its built output) or from the pipeline's build lines run once in the pod with corestack_exec_command on the row's Node.
  19. Carry the old host's own scheduled jobs — the target keeps only its own entries, so anything the source's crontab ran for the application is lost unless you move it. From step 1's crontab -l (and, when the person can read them, the application's lines in /etc/cron.d), leave out what the platform already runs — WordPress wp cron event run / wp-cron.php; Magento bin/magento cron:run (and the legacy update/cron.php, setup:cron:run); Laravel artisan schedule:run; Shopware scheduled-task:run and any messenger:consume (the built-in line and the queue container do those) — and translate every other line into one corestack_crons_update entry: label (what it does, ≤ 60), schedule in the form corestack_crons_get shows (an @reboot line has no equivalent — tell the person), command with the old paths replaced by <site-root>/htdocs and any absolute PHP binary (/usr/bin/php, /opt/…/bin/php) by php, no_overlap true, timeout the smallest of 900 / 3600 / 21600 that covers it, and enabled false. Save them with the whole set, in the same update that switches Scheduled tasks off (rule 9) — at most 49 entries; a variable line (MAILTO=…) has no field: tell the person. Show the person the list and ask which to run; step 10 of cutover-and-rollback switches the approved ones on, with the site switch, at cutover.

Steps

  1. Inspect the old host (read-only):
    sh
    cd <old-root>
    php artisan --version; php -v; composer show laravel/framework | head -3
    php artisan about --only=environment,drivers 2>/dev/null
    grep -E '^(APP_URL|QUEUE_CONNECTION|CACHE_(DRIVER|STORE)|SESSION_DRIVER|FILESYSTEM_DISK|BROADCAST_)' .env
    php artisan schedule:list; ls -la public/storage; du -sh storage/app; crontab -l
    grep -rhoE -- '--queue=[^ ]+' /etc/supervisor* 2>/dev/null; ps -eo args | grep -E '[q]ueue:(work|listen)'
    Note every queue the old workers listen on (--queue=): the target's workers process the default connection's own queue, so jobs sent to any other queue wait there. Say so to the person before the cutover.
  2. Facts and verdict with application: "laravel" (placement before the create, site_id after it — rule 1).
  3. Target: content: "empty", the verdict's PHP / MariaDB (an existing target's versions: rule 1); an existing Git-mode target goes to manual first (rule 7).
  4. Excludes:
    Text
    /.env
    /vendor/
    /node_modules/
    /storage/framework/cache/data/
    /storage/framework/sessions/
    /storage/framework/views/
    /storage/framework/down
    /storage/framework/maintenance.php
    /storage/logs/
    /bootstrap/cache/*.php
    /public/hot
    /public/storage
    /.git/
  5. Files: rule 4 into htdocs.
  6. Database: under the web hold (rule 9), dump, leaving out the rows of cache, cache_locks and sessions and — in a trial copy only — jobs and job_batches (structure kept), so a trial never runs the source's queued jobs; the cutover's final dump keeps jobs and job_batches (step 7 of cutover-and-rollback); failed_jobs is data and always travels; corestack_db_import {…, drop_existing_tables: true, confirm_domain}.
  7. .env — write it with corestack_file_write: the source's file with these keys set as the platform writes them:
    Text
    APP_ENV=production
    APP_DEBUG=false
    APP_URL=https://<platform-host>
    DB_CONNECTION=mysql
    DB_HOST=127.0.0.1
    DB_PORT=3306
    DB_DATABASE="${APP_DB_NAME}"
    DB_USERNAME="${APP_DB_USER}"
    DB_PASSWORD="${APP_DB_PASSWORD}"
    REDIS_HOST=127.0.0.1
    REDIS_PORT=6379
    SESSION_DRIVER=redis
    CACHE_STORE=redis            # CACHE_DRIVER on Laravel 10
    QUEUE_CONNECTION=database
    DB_QUEUE_TABLE=jobs
    Keep APP_KEY and the application's own keys. The containers' own DB_* and REDIS_HOST, and MAIL_* once the row has a mode, win over .env (Dotenv never overrides a set variable).
  8. Cron off until cutover — rule 9's hold, set before step 6's import and checked here (corestack_crons_get shows enabled and builtin_enabled false): the built-in schedule:run runs on a row that is not live yet, and the copy must not send the application's scheduled mail or charges. storage/framework/down and maintenance.php are excluded from every pass (step 4), so the source's php artisan down at cutover (step 5 of cutover-and-rollback) never reaches the target.
  9. Build (corestack_exec_command):
    sh
    composer install --no-dev --optimize-autoloader --no-interaction
    php artisan storage:link
    php artisan migrate:status          # run `php artisan migrate --force` only if the code is newer than the data
    php artisan optimize:clear && php artisan optimize
    php artisan queue:restart
    Front-end assets: set the environment's Node.js version first (corestack_node_version_change, matching the old host's .nvmrc / engines, rule 18); copy the old host's public/build with the files, or run npm ci && npm run build once in the pod on the row's Node; carry the build into the pipeline (the vite / laravel_mix preset, or the old lines checked and saved — rule 18) and rehearse it on staging.
  10. URLs: corestack_site_rewrite_urls {…, from_hosts: [<domain>]} changes APP_URL through the platform's boot handshake; or strategy 2. URLs inside the application's own data are the application's to change.
  11. Test: /, /login, /up (Laravel 11 and later), the application's own health or API routes. Then corestack_site_laravel_queues_get {site_id}: unworked must be empty — a queue there holds jobs no worker takes (the step 1 queues); tell the person which, and that Corefinity support can have them worked.
  12. Cutover: the cutover-and-rollback playbook; the cron goes back on there.
Was this helpful?
Open in ClaudeOpen in ChatGPT