Problem after Updating to v28

ā„¹ļø Support šŸ“¦ Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
23

because the value depends on the timezone youā€™re in, and when you want the maintainenance window to start.

I donā€™t use the NC Docker images, but as far as I understand it, thatā€™s what environment variables are for: GitHub - nextcloud/docker: :ferry: Docker image of Nextcloud

24

My previous post obviously was about the maintenance_window_start parameter.

As for the bz2 package, I honestly donā€™t understand it either, why they donā€™t just include it. Thereā€™s a discussion about it on GitHub, and as far as I can remember itā€™s only needed in very few situations, so you can probably just ignore the warning.

25

truly, NC is a big machinery and you can die tryinā€™
Iā€™m not using sudo if i need to log in and access the container, I lazily use root huhu
But we all know I wouldnā€™t do that in my Debian, right?
peace :v:

26

Easy way to do this:

  1. Delete all entery in /path/to/nextcloud/data/nextcloud.log
  2. add ā€˜logfileā€™ => ā€˜/path/to/nextcloud/data/nextcloud.logā€™, to /path/to/nextcloud/config/config.php
  3. done