Updating Bacularis

General notes

Before upgrading please read the release notes in the Bacularis GitHub project on the Releases page in each Bacularis repository.

Binary packages update

For binary packages the upgrade procedure is automated and no additional action is required. The only command to run is the upgrade command by the system package manager.

Composer project update

For installations by Composer Bacularis stores own configuration inside the vendor directory. This configuration has to be preserved between updates. For this purpose on the Composer update command Bacularis creates in the project directory a TAR archive with configs and logs and restores them to the original locations just after successfull update.

From the above reason, to upgrade by Composer you need to have TAR archiver installed in the operating system and available in the system PATH.


Before upgrading please download from the project on GitHub https://github.com/bacularis/bacularis-app the latest composer.json file. Then copy it to the Bacularis project directory on local filesystem to replace the original composer.json file. This step is needed because Composer does not provide any way to update project files created by composer create-project command.

All upgrade process consists of running one Composer command. You can run it in one of two ways:

[EXPERTS ONLY] run upgrade as regular user

It is case running upgrade as any user that have read/write access to the all local Bacularis project files or that is theirs owner. At the end of successfull upgrade, you will see list of directories for which you will need to set read/write permissions for the web server user. Before doing it, please make sure that the system user is owner of all Bacularis files. Below you can see how to upgrade as the www-data user from the root user account:

cd /var/www/bacularis-app
chown -R www-data:www-data .
sudo -u www-data composer update