If you are at the wrong address you will be told to go to the public folder.
Once open, you will be redirected to the install procedure. Completed you will be able to create an admin account and enjoy Lychee.
The process is described here.
To back up your Lychee installation you need to perform the following steps:
/var/www/html/Lychee):.env
public/dist/user.css
public/uploads/
mysqldump -u user -ppassword --databases lychee_database > lychee_backup.sql
Replace user, password, and lychee_database by the values of DB_USERNAME, DB_PASSWORD, and DB_DATABASE from the .env file in the Lychee folder.
mysql -u user -ppassword < lychee_backup.sqlhttps://example.dev/lychee/Yes, here is a configuration to help you:
location ^~ /lychee {
alias /var/www/lychee/public;
index index.php;
try_files $uri $uri/ @lychee;
location ~ \.php$ {
if (!-e $request_filename) {
rewrite ^/lychee/?(.*)$ /lychee/index.php?/$1 last;
break;
}
fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $request_filename;
}
}
location @lychee {
rewrite /lychee/(.*)$ /lychee/index.php?/$1 last;
}
https://example.dev/lychee/Yes, the process is described here.
app/?From #311
Short answer: Lychee will work without a writable app/ folder.
However, if you want to be able to update your Lychee installation with a click of a button in the web browser (though it's disabled by default), your whole Lychee installation tree (and not just app/) must be http-writable.
As far as I know, the minimum set of directories that need to be http-writable is as follows:
storage/
public/uploads/small
public/uploads/big
public/uploads/thumb
public/uploads/medium
public/uploads/import
public/dist
You go to Diagnostics ↠ Check for Updates
Once done you need to update the Diagnostic page (click on it again in the left menu)
You will see a Apply Update button on the top. Click on it and done.
If it breaks (error 500) you can still go back to command line and do your git pull, migrate etc...
There are some securities that you need to disable via the advanced settings menu:
.env specify production:force_migration_in_production = 1apply_composer_update = 1 (optional)The second one is really optional if updates don't need the composer (like 90% of the time) then it can just stay at 0.
Yes, but it's not trivial or recommended. After copying the database:
1. Download this file to your database/migrations/ folder.
2. Run the SQL command delete from migrations where migration='2019_04_07_193345_fix_32bit'; to make sure it will run.
3. Run php artisan migrate. This should run a one-off migration that was originally added to allow 32-bit systems to migrate from Lychee v3.
This will only work on top-level albums. Subalbums will require manual intervention.
git installation and not a downloaded releasemaster branch.gitexec is available.allow_online_git_pull setting is set to 1artisan migrate and composer from running after every git pull?We've set composer to install git pre-commit and post-merge hooks by default.
- The pre-commit is to help developers by checking and fixing and code style problems before they hit our testing. If you aren't committing and changes, this will not be run.
- The post-merge ensures that your dependencies and database version are kept current. This can be disabled by creating a file .NO_AUTO_COMPOSER_MIGRATE in your Lychee root and deleting (if necessary) .git/hooks/post-merge. If you disable this script, you will need to run composer and artisan migrate manually. Alternatively, the Update UI can be set to handle this if you run your updates there.
{tip} Caught a mistake or want to contribute to the documentation? Edit this page on Github!