Clear logs?

[gardiol]

My lychee installation has a huge logs table in the database... I mean over 115mb when exported. Is possible to have a way to limit log size or purge/clear from UI?

[ildyria]

php artisan lychee:logs clean

This will clear the log database.

[ildyria]

from the UI there should be a button to remove the Notice and Warnings

[gardiol]

There is... but my table grow so big that the web page timed out before any log was shown... and the button did not work i guess for the same reason. At that point, i cleared the table from phpmyadmin,... Good to know the artisan command.. Still would be useful to prevent this situation. Also, logging on database seems... odd. Is there a reason a normal file is not used? For example i cannot parse the database with logcheck.

[ildyria]

Well the initial Lychee was logging on Database, we did not change that. Also it is easier to retrieve and manage than files...

Laravel do logs their error in files but the problem is that it is then quite hard to read and it is more dev oriented...

[ildyria]

There is... but my table grow so big that the web page timed out before any log was shown... and the button did not work i guess for the same reason.

There is also another way but not advertised. 😇 (Sorry)

If you are logged in as admin and you go to https://example.com/api/Logs::clear (GET request) it will do the same as php lychee:logs clean

[gardiol]

Yes but a growing log in a database can be a problem.
Also, cannot be analyzed with standard server log check tools.

I do backups, of course who don't, of my server, and 116mb of log was a bit strange, indeed the Lychee mysql backup was even bigger than my NextCloud instance backup, weird.

Maybe it was so big because i have debug enabled?

Indeed not a major issue at all, but my guess something should be considered.

[ildyria]

That is really surprising... My log database is 4 Mio (14 400 lines) and I have 12 155 lines in my Photo table.

[ildyria]

You should have a look what are the warnings in it. I find this pretty strange.

[gardiol]

i had over 250K lines... My guess is most where due to the various "upgrades" i did from Lychee 3 to Lychee 4 and then to git build... then i forgot composer install and artisan migrate.. All things considered...
Also i loaded hundreds of thousands of pictures in this convoluted timeframe...

I am sorry i deleted the rows before actually saving them.. I could fetch yesterday backup and check if you think it's important

[ildyria]

Also, you can just do compose install --no-dev :)

[ildyria]

Nah it should be fine, you can just upload new pictures, if something is wrong you will see warnings poping up again. :)

[ildyria]

Did the upgrade from v3 to v4 went smoothly ?

[gardiol]

I now have this little upgrade script:

#!/bin/bash
git pull
php composer.phar install --no-dev
php artisan migrate

Might be interesting for other users.
The upgrade went well.. i did it more or less two months ago. Absolutely painless and no issues...

[ildyria]

I would add a chown -R www-data:www-data * in it just to make sure that the ownership are correct if your web user is www-data (at least that the case for apache). :)

Happy to hear that the upgrade went painlessly. 🎉

[gardiol]

I prefer not to, for security reasons... I have my "storage" and "public/upload" folders assigned to group "apache" with g+w permissions... So far it seems to be enough... is it?

[ildyria]

oh sure. :) that was if you wanted to make the update directly from the GUI. :)

[gardiol]

Is it possible to do the update directly from the GUI? How?
Lychee is a marvel.. I just discovered the artisan lychee:sync command and i am loving it...

[ildyria]

Is it possible to do the update directly from the GUI? How?

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:

• you need to allow update is your .env specify production:
  force_migration_in_production = 1
• you need to allow composer :
  apply_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. :)

Hidden tip: to quickly make the login dialog show, you can just press L instead of having to click on the Login button. 😇