2.0.22, skipping everything between.
rm -r var/plugins/* rm -r var/cache/* bin/console kimai:reload
Change into your Kimai directory, then fetch the latest code and install all dependencies:
git fetch --tags git checkout 2.0.24
You might have to prefix the next commands with
php (depends on your environment):
Update all composer dependencies:
composer install --optimize-autoloader -n
And run the Kimai updater:
Remember to adjust the file permissions if necessary.
You have to allow PHP (your webserver process) to write to
var/ and it subdirectories.
Here is an example for Debian/Ubuntu (to be executed inside the Kimai directory):
Test Kimai before executing these commands (they are likely not required in a shared-hosting environment).
You probably need to prefix them with
the group might be called different than
That’s it, Kimai is running the most current version. Enjoy the latest time-tracking features!
If you see the following error during
composer install, then you are running a very old installation 😁
curl error 6 while downloading https://flex.symfony.com/versions.json: Could not resolve host: flex.symfony.com
Great that you like Kimai, but PLEASE: for various reason (like security) you should update more regularly!
composer install --optimize-autoloader -n --no-plugins --no-scripts once and then follow the normal update process.
Please check with
git status if your directory is without changes, to make sure you really can upgrade.
If the following statement looks different for you, keep on reading:
$ LANG=en_US git status Not currently on any branch. nothing to commit, working tree clean
If you experience an issue like this (file name can vary) while performing the
error: Your local changes to the following files would be overwritten by checkout: symfony.lock Please commit your changes or stash them before you switch branches.
config/routes/annotations.yaml: needs merge error: you need to resolve your current index first
This means you have changes in at least one of the files in your installation. This can happen by installing additional packages (e.g. for LDAP), or simply when you changed a configuration file (which was not meant to be changed, read the docs how to apply config changes in a safe manner).
These changes need to be reverted before the update can be executed.
One possible solution is to use
git stash, which will store your changes in a temporary location.
If that fails for some reason, the other (rather extreme) option is to run
git reset --hard,
which will wipe all local changes.
Please read GIT docs on how to fix that, it is NOT related to Kimai.