The way you can update Lychee depends of how you did your installation:
git clone
then you can either use a similar process or do it directly online via the Graphical User Interface of Lychee.Don't forget to take a look at the Changelog to see what's new and to check for any actions that may be required.
Fully updating Lychee with git
is the easiest way:
# download the lastest files
git pull
# update the dependencies
composer install --no-dev
# apply the database migration
php artisan migrate
If you have the post-merge
hook set up the following is enough:
git pull
This update will be the one you have to use if you are following the Release channel.
public/uploads/
, public/dist/user.css
and .env
(and database/database.sqlite
if using SQLite as your database)Diagnostic
page and click on the Apply migration
button.This requires:
git
to be installedwww-data
for apache2) to all the folders, files and .git/
.exec
to be available as a php function.allow_online_git_pull
has to be set to 1
Notice that Lychee version (git) tells you:
However you should see a "check for Updates" button:
If you click on it, it will ask your server to check how far behind you are from the bleeding edge version of Lychee:
Notice that Lychee version (git) now tells you:
By clicking on "Update available" this will trigger server side a git pull
and artisan migrate
.
You can see the log result of the command line printed above the diagnostic information. By default composer calls are disabled.
We can once again check for updates:
And we are done.
{tip} Caught a mistake or want to contribute to the documentation? Edit this page on Github!