3
0
mirror of https://github.com/jlu5/PyLink.git synced 2024-12-17 23:52:49 +01:00

Refresh permissions examples, adding a stub in the main example conf for admin access

This commit is contained in:
James Lu 2016-12-09 20:57:24 -08:00
parent 57aa844fcb
commit 1e7210a6db
2 changed files with 23 additions and 5 deletions

View File

@ -57,6 +57,14 @@ login:
# (plain text) for backwards compatibility.
encrypted: true
permissions:
# Permissions are described in more detail in example-permissions.yml.
# Replace ABC123 with your PyLink account name (configured above)
# in order to give yourself admin access.
"$pylinkacc:ABC123":
- "*"
servers:
# Please note: these are only EXAMPLE link blocks. You should edit them and
# remove ones that you don't need in your config.

View File

@ -1,11 +1,9 @@
# This file is an example of the permissions system in PyLink. Should you wish,
# you may copy the contents of this file and paste it into the configuration you're
# using.
# Permissions work by mapping hostmasks or exttargets to list of permissions, allowing
# Permissions work by mapping hostmasks, accounts, and exttargets to lists of permissions, allowing
# you to fine tune which users have access to which commands.
# The permissions API is new, and optional for plugins. Currently, only Automode and Relay use it.
# If you do not specify any permissions block in your configuration, PyLink will default to a
# permission set defined by plugins, which usually correspond to the list below, but can be
# changed on every release.
@ -30,8 +28,20 @@ permissions:
- automode.list
# These allow opers to manage Relay links on their network.
- relay.create
- relay.destroy
- relay.claim
- relay.link
- relay.delink
- relay.linkacl.view
- relay.linkacl
"*!*@*":
# The following permissions are given to all users by default.
- relay.linked
"$pylinkacc":
# Those with an admin login in PyLink can do anything.
# Replace ABC123 with your PyLink account name (configured above)
# in order to give yourself admin access.
"$pylinkacc:ABC123":
- "*"