We run gravcms in a linux container (lxd) which has build in snapshot support. Therfore we don’t want to use gravcms’ backup mechanism.
What is the best way to completely disable the whole backup job execution without disabling the other jobs? What is the intended way to configure jobs in a multisite install? The admin plugin creates a config in every site which causes job execution to run for every site instead of once for the hole grav install, right?
I disabled backup schedule in all site config files but the job is still being executed.
find . -name backups.yaml|xargs grep 'schedule:' ./sites/main/config/backups.yaml: schedule: false ./sites/doc/config/backups.yaml: schedule: false
Do I have to create a backup job config for the main config in
grav/user/config to prevent the backup job execution at all? We don’t use grav/user/pages but only grav/sites
I also tried to disable the job execution by setting
max_backups_count: 0 but this doen’t work either since this config parameter seems only to be used by the purge job.