-
Notifications
You must be signed in to change notification settings - Fork 12
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
ACL options #16
Comments
At the moment you could specify them in the |
Do I have to use a specific formatting for the options inside that hash? thanks. |
You could try putting the option names with spaces in |
I see. Will test on a non-productive machine first ;-) (always a good idea). |
Sure, however if you want to do a PR, do it against the new More info here: https://lists.debops.org/pipermail/debops-users/2017-October/000102.html |
Let me be lazy for now and paste my example in here. PR later, ok?
tested right now, generates working config on target machine. |
Sure, sounds good. |
forked/cloned your new repo (great work, btw!) but can't find the sources for the docs in there. Did some finds and greps ... pls advise. |
Currently the documentation is still in the role directories. The |
So PR against this repo here instead? |
No, if you want to do a PR, please do it against The old role repositories will become read-only. I plan do write a script that will extract the roles from the monorepo and publish them so that they can still be accessed via Galaxy, in a somewhat simple form. |
OK, understood. I will do that asap. |
how to get options deployed like in
https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs#Enable_Extended_ACL_Support_in_the_smb.conf_File
?
Do they have to be added to the role or may they get added within some specific (and existing) variable?
The text was updated successfully, but these errors were encountered: