I run a Nextcloud instance with chroot enabled for PHP-FPM. This causes an issue; the interpreter for web-based usage is fpm, whereas the cronjobs are executed from the cli interpreter, which doesn't support the chroot option.
I have worked around this by editing the data directory, which is occasionally overwritten by Nextcloud, causing the cronjobs to fail.
Steps to reproduce
- Enable the
chroot functionality of PHP-FPM.
- Open config.php and edit the datadirectory variable like
'datadirectory' => ((php_sapi_name() == 'cli') ? '/var/www' : '') . '/nextcloud-data',.
- Set the cronjob as per the official documentation.
Expected behaviour
I expect the datadirectory variable to remain untouched.
Actual behaviour
Updates (both minor and major) change the datadirectory variable to exclude the custom sapi rewrite. This happens since at least v15.
I run a Nextcloud instance with
chrootenabled for PHP-FPM. This causes an issue; the interpreter for web-based usage isfpm, whereas the cronjobs are executed from thecliinterpreter, which doesn't support thechrootoption.I have worked around this by editing the data directory, which is occasionally overwritten by Nextcloud, causing the cronjobs to fail.
Steps to reproduce
chrootfunctionality of PHP-FPM.'datadirectory' => ((php_sapi_name() == 'cli') ? '/var/www' : '') . '/nextcloud-data',.Expected behaviour
I expect the datadirectory variable to remain untouched.
Actual behaviour
Updates (both minor and major) change the datadirectory variable to exclude the custom sapi rewrite. This happens since at least v15.