I have a nextcloud install that work fine as a container.
I was wonderring why each time I do the following command:
docker compose down && docker compose up -d
I get this:
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
I have this as a config for log:
'datadirectory' => '/data',
'log_type' => 'file',
'logfile' => 'nextcloud.log',
'loglevel' => 2,
'logdateformat' => 'Y-m-d H:i:s',
'log_rotate_size' => 104857600,
nextcloud.log should go into /data, no?
why goes it into /var/www/html?
/var/www/html is the “default” directory things like Apache use as a webserver root.
If you have nothing in it, then its normally safe to drop as you serve sites from a different folder.
in all honesty, for simplicity what I tend to do is: Create a /var/www/html/index.php file ( The only file in that folder )
The data directory resides within /var/www/ structure
As you are using docker you can make this location wherever you prefer, but this is the location your container is stupidly assuming. Make sense?
Found this explanation with a basic internet search. It came from digital ocean
here is the nextcloud documentation:
Citation: logging_configuration file
All log information will be written to a separate log file which can be viewed using the log viewer on your Admin page. By default, a log file named nextcloud.log will be created in the directory which has been configured by the datadirectory parameter in
So it should go into datadirectory whitch is for me /data.
But it is not the case? Why?
I update nextcloud to 23.0.5.