Updating

One Composer command. Your settings stay, and the database and the widget follow by themselves.

One Composer command, in your project folder:

cd /var/www/your-site
composer update opensolr/chat-bot-client

To see which version you have, before or after: composer show opensolr/chat-bot-client.

01 · What stays as it is
  • Your settings, your logo and the admin password, in the data folder. Composer never touches it.
  • Your copies of index.php and .htaccess in the chat’s folder of your web root. They are yours, not part of the package.
  • The script tag in your pages.
02 · What follows by itself
  • The database. When a new version needs a change in it, the change is made on the first request after the update. Going back to an older version after that is refused with The database was made by a newer version of this package.
  • The chat window. Browsers check the script on every page load and take the new one as soon as it changed, so visitors get the new window on their next page view.
03 · PHP’s own cache

If PHP keeps compiled files in its opcache without checking them for changes (opcache.validate_timestamps=0), it goes on running the old version until PHP-FPM is reloaded:

sudo systemctl reload php8.3-fpm

With the default settings PHP notices the new files by itself within a couple of seconds and no reload is needed. A reload can cut an answer that is being written at that moment; the visitor only has to ask again.

04 · What changed

Every change is in the history on GitHub, and every version is on Packagist.

The Opensolr Chat Bot Client is open source and MIT licensed. Questions about your Opensolr account, index or plan go to opensolr.com/contact; questions about the client itself belong on GitHub.

Opensolr Chat Bot Documentation