Exclude folders from updater check

My nextcloud installation is also used to verify login for a script that runs on the same server. This script needs to be located in the same directory as nextcloud in order to use the nextcloud cookie. I can’t however not find a way to update nextcloud when doing this, it cries about this extra folder even when using

‘integrity.check.disabled’ => true,

in the config.php file.

I have also tried to find other ways to make nextcloud verify the login for this script but so far this seems to be the only way. The script is included in nextcloud as a “external site”.

Is there a way to fix this problem? CLI, disable check or maybe using a token of some sort? It is fairly annoying that I never can update nextcloud.

No one knows?

This is how I do it:

In my example I assume the following circumstances:

  • Web server: apache2
  • nextcloud installation directory: /var/www/nextcloud
  • extra folders to be created: /admin

So the folder should be accessible via https://mycloud.domain.tld/admin/

Now a directory is created elsewhere in the file system that contains all the files that should be in the admin folder. For this example, let’s assume:

  • Directory containing admin files: /data/nextcloud/admin-folder

Now you create a file /etc/apache2/sites-available/nextcloud-admin

with this entry:

Alias /admin /data/nextcloud/admin-folder
# here comes all the rest you need for this folder

Now run

sudo a2ensite nextcloud-admin
sudo systemctl reload apache2

and now the extra folder admin is included in your server tree and no updater will ever see it.

The name “admin” is an assumption, you can try other names but you will have to test it thoroughly, some names will not work or cause weird problems.

I hope this helps.

Much luck,

1 Like

This is awesome! Thanks for the help, all updated now :slight_smile:


This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.