Updating

The self-hosted version supports automated updates that will notify admin users whenever new packages are available for download.

Automatic Updates

Clientverse includes a built-in update mechanism. When a new version is available, administrators will see a notification in the settings panel. To update:

  1. Log in with an administrator account
  2. Navigate to Settings
  3. If an update is available, you'll see an update notification with the new version number
  4. Click the Update button to start the process
  5. Wait for the process to complete — do not close your browser during the update

Important: Make sure the Clientverse installation directory is writable so that the modified files can be replaced and the old ones can be removed. Clientverse also requires the PHP Zip extension to be installed for the update process to work.

Manual Update

If the automatic update fails or you prefer to update manually:

  1. Download the latest release from the Clientverse GitHub Releases page
  2. Back up your current installation (especially the .env file and database)
  3. Extract the new release files over your existing installation, replacing old files
  4. Restore your .env file if it was overwritten
  5. Run php artisan migrate to apply any database schema changes
  6. Clear the application cache with php artisan cache:clear and php artisan config:clear

Tip: Always create a full backup before updating. You can back up your database with mysqldump -u user -p clientverse > backup.sql and copy the entire Clientverse directory.

Checking Your Current Version

You can find your current Clientverse version in the Settings panel under system information, or by running php artisan --version from the command line.

Version-Specific Upgrade Notes

Steps:

  1. Make sure your server is running PHP v8.0+
  2. Make sure the entire Clientverse directory is writable 777 (the PHP process should be able to make changes to the file system).
  3. Go to the settings page and click the update button.
  4. An error will be displayed due to the Laravel upgrade, that's fine this time.
  5. Finalize the upgrade by running php artisan refresh from the terminal.

If you are still facing errors with your installation, check the following places for further information:

  • storage/logs/update-***.log for updater logs
  • storage/logs/laravel-***.log for framework logs
  • /var/log/apache2|nginx/error.log for server logs

Upgrading from 1.0.0-beta.3 to 1.0.0-beta.4

Steps:

  1. Make sure your server is running PHP v8.0+
  2. Make sure the entire Clientverse directory is writable 777 (the PHP process should be able to make changes to the file system).
  3. Go to the settings page and click the update button.
  4. An error will be displayed due to the Laravel upgrade, that's fine this time.
  5. Finalize the upgrade by running php artisan refresh from the terminal.

If you are still facing errors with your installation, check the following places for further information:

  • storage/logs/update-***.log for updater logs
  • storage/logs/laravel-***.log for framework logs
  • /var/log/apache2|nginx/error.log for server logs

Upgrading from 1.0.0-beta.2 to 1.0.0-beta.3

Steps:

  1. Make sure your server is running PHP v8.0+
  2. Make sure the entire Clientverse directory is writable 777 (the PHP process should be able to make changes to the file system).
  3. Go to the settings page and click the update button.

Upgrading from 1.0.0-beta.1 to 1.0.0-beta.2

Steps:

  1. Make sure your server is running PHP v8.0+
  2. Make sure the entire Clientverse directory is writable 777 (the PHP process should be able to make changes to the file system).
  3. Go to the settings page and click the update button.

Upgrading from 1.0.0-alpha.1 to 1.0.0-beta.1

Steps:

  1. Make sure your server is running PHP v8.0+
  2. Make sure the entire Clientverse directory is writable 777 (the PHP process should be able to make changes to the file system).
  3. Go to the settings page and click the update button.