Hey there.
I've been managing a bigger nextcloud instance and stumbled upon a problem while migrating data from the native data folder to a symlink of another folder.
In our exact scenario, we want to use another path (for example /mnt/nextcloud) and make a symlink from /opt/nextcloud-data to /mnt/nextcloud.
The problem in this being, that the puppet module doesn't allow me to define another folder or symlink, since that directory is already a defined object:
|
file { $nextcloud::datadir: |
|
ensure => directory, |
|
owner => $nextcloud::system_user, |
|
group => $nextcloud::system_group, |
|
before => Nextcloud::Install::Distribution['initial install'], |
|
} |
It would be great to have a toggle, that allows me to "skip" the automatic creation of the data folder in order to define my own puppet file element with a toggle like manage_datadir => false.
Hey there.
I've been managing a bigger nextcloud instance and stumbled upon a problem while migrating data from the native data folder to a symlink of another folder.
In our exact scenario, we want to use another path (for example /mnt/nextcloud) and make a symlink from /opt/nextcloud-data to /mnt/nextcloud.
The problem in this being, that the puppet module doesn't allow me to define another folder or symlink, since that directory is already a defined object:
puppet-nextcloud/manifests/install.pp
Lines 7 to 12 in d5be5c7
It would be great to have a toggle, that allows me to "skip" the automatic creation of the data folder in order to define my own puppet file element with a toggle like
manage_datadir => false.