Reticulum Manual 91/128
Git Over Reticulum (cont.)
Additionally, they can be configured in a group group_name.allowed file, placed next to the group_name group directory.
Repository-Level Configuration
Repository-specific permissions are set in .allowed files placed next to the repository directory (for example, myrepo.allowed for myrepo):
# myrepo.allowed
r:all
w:9710b86ba12c42d1d8f30f74fe509286
rel:9710b86ba12c42d1d8f30f74fe509286
Dynamic Permissions
Permission files can be made executable to generate permissions dynamically:
$ chmod +x myrepo.allowed
When executable, the script is run and its stdout is parsed as permission rules. This allows integration with external authentication systems.
Work Document Permissions
Work documents support additional permission granularity through .allowed files in the work directory (e.g., 42.allowed for document #42). These files use the same permission syntax but only support:
• r (read) - View the document
• w (write) - Edit the document
• i (interact) - Comment on the document
• p (propose) - Propose changes (future use)
• adm (admin) - Full control over the document
Document permissions override repository permissions for that specific document. Work document permissions can be updated simply by editing the .allowed file, or remotely by using the rngit work command.
Creator Permissions
When a user creates a repository (via create, fork, or mirror), they are automatically granted adm (admin) permissions on that repository.
When a user creates a work document, they automatically receive interact and write permissions on that document.
Permission Examples
Example 1: Public Read, Restricted Write
r:all
w:9710b86ba12c42d1d8f30f74fe509286
Everyone can read, only the specified identity can write.
Example 2: Collaborative Development
r:all
i:all
p:all
w:9710b86ba12c42d1d8f30f74fe509286
rel:9710b86ba12c42d1d8f30f74fe509286
Everyone can read, interact (comment), and propose work documents. Only the specified identity can write, create releases, and manage work documents fully.
Example 3: Private Repository
rw:9710b86ba12c42d1d8f30f74fe509286
rw:a1b2c3d4e5f686ba12c42d1ba12ef1aa
Only the two specified identities have any access (read or write).
Example 4: Mirror with Stats
r:all
s:all
w:none
Everyone can read and view stats, but nobody can push (mirror is read-only from upstream).
Permission Short Forms