Knowledgebase

Migrating a Custom Application Print

  • developersgitdeployment, developers, migration, database, cron, ssl, php, uploads, permissions, dns
  • 0

Moving something you built yourself.

WHAT TO MOVE

Application code The database Uploaded files and generated assets Configuration, recreated rather than copied Cron jobs Any SSL certificates installed manually

THE SEQUENCE

  1. Set up the destination: PHP version, extensions, database.
  2. Deploy the code, ideally by cloning from the repository.
  3. Install dependencies.
  4. Import the database.
  5. Create the configuration file with the new credentials.
  6. Copy uploads and generated files.
  7. Set permissions and ownership.
  8. Recreate cron jobs.
  9. Test with a hosts file entry.
  10. Change DNS.
  11. Keep the old environment for a week.

WHAT PEOPLE FORGET

Cron jobs File permissions after copying The storage symlink, in frameworks that use one

Environment differences: PHP version, missing extensions

Hardcoded absolute paths in configuration

VERIFYING

Every page type, every form, login, and any integration. Not just the homepage.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot