On 6/7/24 03:44, David Runge wrote:
IIRC, the above changes are something that nextcloud itself adds to the file during initial configuration. If you want to continue running nextcloud as before you will want to keep those lines. The `DO NOT CHANGE ANYTHING ABOVE THIS LINE` comment implies that anything above that line is vendor provided (coming from nextcloud upstream) though and should always be kept in sync with changes provided by updates.
As an aside: This is why the/etc/webapps/nextcloud/.htaccess file is owned by the nextcloud user and/usr/share/webapps/nextcloud/.htaccess is a symlink to it.
Similar to other files that are tracked in the context of the backup array [1] of a package you are expected to adapt the file accordingly (this has been the case for many nextcloud versions already) and not necessarily apply all changes provided by the updated file (this is also the case for other packages FWIW, as you often want to keep your specific modifications).
I hope this clears things up.
It does and that it kind of what I thought. The diff output shows the top (upstream provided) part of .htaccess is still identical. What was strange is that the Arch config seems to come and go at times in the .htaccess.pacnew file. The way I do it when I get a nextclound .htaccess.pacnew is I rename it .htaccess.yyyymmdd with the current date and then use a symlink to switch to the new once after I compare changes. But this time I noticed the .htaccess had lost about 1K of text. It had done that before as well, e.g.: lrwxrwxrwx 1 root root 18 Jun 6 20:58 .htaccess -> .htaccess.20240523 -rw-r--r-- 1 nextcloud nextcloud 4367 Oct 5 2023 .htaccess.20231005 -rw-r--r-- 1 nextcloud nextcloud 4391 Feb 1 20:23 .htaccess.20231027 -rw-r--r-- 1 nextcloud nextcloud 3993 Feb 29 11:20 .htaccess.20240301 -rw-r--r-- 1 nextcloud nextcloud 5188 May 20 14:22 .htaccess.20240520 -rw-r--r-- 1 nextcloud nextcloud 5149 Jun 6 21:32 .htaccess.20240523 -rw-r--r-- 1 nextcloud nextcloud 5188 May 20 14:22 .htaccess.20240523.old -rw-r--r-- 1 nextcloud nextcloud 3954 Jun 6 08:57 .htaccess.20240606 Above you can see the March 1 .htaccess had lost about the same ~1K bytes as the June 6 .htaccess did. I know I've scratched my head on this before, but I don't know if I ever got to the bottom of the atavistic text. Either way, the text not being in the new .htaccess kills the server dead when installed to /docroot/nextcloud I'll investigate further. -- David C. Rankin, J.D.,P.E.