Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config option to deactivated skelekton #82

Closed
unclesam87 opened this issue Jul 2, 2024 · 3 comments · Fixed by #87
Closed

config option to deactivated skelekton #82

unclesam87 opened this issue Jul 2, 2024 · 3 comments · Fixed by #87

Comments

@unclesam87
Copy link

hey,
i am not quite sure how to achieve that:
i want to add the config option to deactivated the skeleton - but when i add the line like that
skeletondirectory: ''"

i get that error:
TASK [systemli.nextcloud : Nextcloud configure: copy skeleton directory] ***********************************************
fatal: [nextcloud.blabla]: FAILED! => {"changed": false, "msg": "dest is required"}

thanks for ur help

@doobry-systemli
Copy link
Contributor

Can you explain what you try to achieve @unclesam87? What do you mean with "deactivate the skeleton"? You don't want any skeleton files to get copied to the folder of new users? Even not the default ones provided by Nextcloud? Then I'd suggest you create an empty directory on the server (e.g. /usr/local/share/nextcloud/skeleton) and put its path into the skeletondirectory variable.

@unclesam87
Copy link
Author

unclesam87 commented Jul 2, 2024

yes i try to get an total empty folder and the normal way to accomplish that is to set an empty selektondirectory in the config.php
from the docu:
'skeletondirectory' => '/path/to/nextcloud/core/skeleton', The directory where the skeleton files are located. These files will be copied to the data directory of new users. Leave empty to not copy any skeleton files.

@doobry-systemli
Copy link
Contributor

Fixed in #87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants