-
Daniel Wisnewski wrote:
Commits were made to release branch, docs.tigase.org shows an old version, perhaps building from master? It should be the last section in Security in the Admin Guide.
Are you sure? I found the ACL doc here: http://docs.tigase.org/tigase-server/snapshot/Administration_Guide/html_chunk/tigase41packetFiltering.html#accessControlList which looks like the document you've added: https://projects.tigase.org/projects/tigase-server/repository/revisions/ffe6669148cf876c68a652e629efd9d6b9d7b6f3/entry/modules/documentation/adminguide/asciidoc/text/Admin_Guide_27_-Security-D-_Access_Control_List.asciidoc
Btw. I would drop numbers in document files names to avoid hassle with renaming everything when you want to insert something in the middle - makes commit smaller and allow to retain document history (easier), v. https://projects.tigase.org/projects/tigase-server/repository/revisions/ffe6669148cf876c68a652e629efd9d6b9d7b6f3
Wojciech, can you have the server build documentation from release branch?
Everything is build from
release
now, and documentation is handled bytigase-server-distribution
- you can check it's configuration.
Type |
Task
|
Priority |
Normal
|
Assignee | |
RedmineID |
2107
|
Version |
tigase-server-7.1.0
|
Tigase offer ability to assign ad-hoc commands to certain users or a group of users. This is kind of a ACL. A proper documentation for this is needed though.
Tigase_ACL.rtf