Before upgrading please read the release notes in the Bacularis GitHub project
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
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
installed in the operating system and available in the system
Before upgrading please download from the project on GitHub
https://github.com/bacularis/bacularis-app the latest
Then copy it to the Bacularis project directory on local filesystem to replace
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:
[RECOMMENDED] run upgrade as root user¶
In this case all file permissions inside the project directory will be set automatically.
[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
www-data user from the
root user account:
chown -R www-data:www-data .
sudo -u www-data composer update