Admin, Restaurant & Website

33. Admin, Restaurant & Website Panel Update

To update the Admin, Restaurant and Website panels, upload the latest source package to the root directory of each respective panel and extract it.

If your project includes custom modifications, we strongly recommend updating with Git so your customisations are preserved while the latest changes are merged in.

Check for a database update first. Every panel package includes its own .sql file. When a release adds or changes tables, that .sql file is updated too — and the new code will not work against the old tables. Read the Changelog for the version you are moving to:

  • If the release mentions database or schema changes — back up your current database, then import the .sql file from the new package into that panel’s database (phpMyAdmin → Import, or mysql -u user -p database < panel.sql).
  • If it does not — leave your database alone; only the source files need replacing.

There is no php artisan migrate step in Foodie, on a fresh install or an update — the .sql file is always the source of truth for MySQL.

33.1. Updating via Git (recommended)

  • Commit and push your existing changes to a dedicated Git branch.
  • Download the latest source package from CodeCanyon.
  • Replace the source files in your working copy with the new version.
  • Review the diff, resolve any conflicts, and confirm your customisations survived.
  • Import the new .sql file if the release changed the database (see the note above).
  • Commit and deploy.

33.2. Replacing the source code

  • Back up your current panel folder and your database.
  • Keep a copy of .env and storage/app/firebase/credentials.json — they are not part of the package.
  • Upload the new package and extract it over the existing installation.
  • Restore .env and credentials.json, then compare .env against the new .env.example and add any new keys.
  • Import the updated .sql file from the new package if the release changed the database. Back up your existing database first — importing replaces the tables it contains.
  • Run the post-update commands:
composer install
php artisan config:clear
php artisan cache:clear
php artisan view:clear

Before you update: take a full backup of the panel folder, the MySQL database and your Firestore data (use the export command in Firestore Database Collection Import / Export). If a release adds new Firestore documents or indexes, re-run the import and index deployment afterwards.