mirror of
https://github.com/jlu5/PyLink.git
synced 2024-11-30 14:49:28 +01:00
34 lines
1.7 KiB
YAML
34 lines
1.7 KiB
YAML
# 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
|
|
# you to fine tune which users have access to which commands.
|
|
|
|
# The permissions API is new, and optional for plugins. Currently, only Automode uses 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.
|
|
|
|
# This determines whether we should merge the plugin-default permissions with the ones specified
|
|
# in the permissions: block. Disabling this allows you greater control over the permissions
|
|
# PyLink gives, but you should check this file on every major update to see if any new permissions
|
|
# were added for commands. Otherwise, commands that were available before may cease to function!
|
|
permissions_merge_defaults: true
|
|
|
|
permissions:
|
|
# Note: It is a good idea to quote any exttargets or hostmasks so the configuration parser knows
|
|
# they are raw strings.
|
|
|
|
"$ircop":
|
|
# The default set of Automode permissions allow you to manage any channels you own in Relay.
|
|
# If Relay is not loaded, this check will fail. This has the ability of allowing local opers
|
|
# to manage their channels, but not abusing Automode to hack modes in other networks' relay
|
|
# channels.
|
|
- automode.manage.relay_owned
|
|
- automode.sync.relay_owned
|
|
- automode.list
|
|
"$pylinkacc":
|
|
# Those with an admin login in PyLink can do anything.
|
|
- "*"
|