GitHub/PyLink
3
0
Fork 0
mirror of https://github.com/jlu5/PyLink.git synced 2024-11-30 14:49:28 +01:00
Code Issues Projects Releases Wiki Activity
https://github.com/jlu5/PyLink
3,668 Commits 5 Branches 72 Tags 7.2 MiB
Python 100%
f17540a7e2
Go to file
James Lu f17540a7e2 README refresh; update supported IRCds list 
- Move charybdis to extended support - I have not seen any networks use this in production
- Move legacy p10 / ts6 variants into a new Legacy support section

[skip ci]
2020-03-14 10:28:21 -07:00
coremods exttarget: use match_text() to match exttarget text fields 2019-12-25 16:04:58 -08:00
docs relay-quickstart: describe delinking another network from our channels 2020-01-09 08:53:44 -08:00
plugins commands.version: replace license notice with (a much more useful) Python version 2020-01-26 13:48:43 -08:00
protocols unreal: update module header 2020-03-08 16:47:31 -07:00
test apply_modes: fix removing multiple ban modes in one command 2019-12-22 23:57:36 -08:00
.dockerignore Add Dockerfile 2019-12-23 00:02:57 -08:00
.gitattributes Actually, use LF line endings for everything 2016-10-27 18:43:57 -07:00
.gitignore Remove log/ from source folder, it's not necessary 2017-08-19 23:23:41 -07:00
.gitmodules Begin integrating ircdocs/parser-tests 2019-09-10 18:11:07 -07:00
.isort.cfg Sort imports via isort 2019-07-14 15:12:29 -07:00
.mailmap Refresh mailmap 2017-07-20 18:46:35 +08:00
.travis.yml Declare Python 3.8 support 2019-12-22 23:13:49 -08:00
AUTHORS AUTHORS: add @IotaSpencer and update my email 2016-11-18 23:16:50 -08:00
classes.py classes: remove self.proto, self.irc compat links 2020-03-08 15:37:06 -07:00
conf.py And now, a test fixture for protocols/ 2019-08-18 16:36:02 -07:00
Dockerfile Add Dockerfile 2019-12-23 00:02:57 -08:00
example-conf.yml example-conf: unmark encoding option as experimental 2020-02-22 23:56:10 -08:00
launcher.py Sort imports via isort 2019-07-14 15:12:29 -07:00
LICENSE.CC-BY-SA-4.0 Relicense docs under CC-BY-SA-4.0 2016-07-09 00:14:24 -07:00
LICENSE.MPL2 Relicense docs under CC-BY-SA-4.0 2016-07-09 00:14:24 -07:00
log.py Sort imports via isort 2019-07-14 15:12:29 -07:00
pylink Sort imports via isort 2019-07-14 15:12:29 -07:00
pylink-mkpasswd Sort imports via isort 2019-07-14 15:12:29 -07:00
README.md README refresh; update supported IRCds list 2020-03-14 10:28:21 -07:00
RELNOTES.md Add changelog for 3.0-rc1 2020-02-22 23:56:27 -08:00
requirements-docker.txt Add Dockerfile 2019-12-23 00:02:57 -08:00
selectdriver.py Revert "selectdriver: actually, force a disconnect when _run_irc() fails" 2018-03-22 21:21:33 -07:00
setup.py Declare Python 3.8 support 2019-12-22 23:13:49 -08:00
structures.py structures: suppress CopyWrapper logging 2019-12-22 22:32:10 -08:00
utils.py Add can-manage-bot-channels protocol capability 2019-11-02 13:55:49 -07:00
VERSION PyLink 3.0-rc1 2020-02-22 23:57:43 -08:00
world.py Sort imports via isort 2019-07-14 15:12:29 -07:00

README.md

PyLink IRC Services

PyPI version PyPI supported Python versions PyPI license

PyLink is an extensible, plugin-based IRC services framework written in Python. It aims to be:

  1. a replacement for the Janus relay daemon.

  2. a versatile framework for developing IRC services.

PyLink and any bundled software are licensed under the Mozilla Public License, version 2.0 (LICENSE.MPL2). The corresponding documentation in the docs/ folder is licensed under the Creative Attribution-ShareAlike 4.0 International License. (LICENSE.CC-BY-SA-4.0)

Support the project

I maintain PyLink and other IRC projects in my spare time - as such, donations are welcome and appreciated.

Donate via PayPal

Obtaining support

First, MAKE SURE you’ve read the FAQ!

When upgrading between major versions, remember to read the release notes for any breaking changes!

Please report any bugs you find to the issue tracker. Pull requests are open if you’d like to contribute, though new stuff generally goes to the devel branch.

You can also find support via our IRC channel at #PyLink @ irc.overdrivenetworks.com. Ask your questions and be patient for a response.

Installation

Pre-requisites

  • CPython 3.5 or above (other intepreters are untested and unsupported)
  • A Unix-like operating system: PyLink is actively developed on Linux only, so we cannot guarantee that things will work properly on other systems.

If you are a developer and want to help make PyLink more portable, patches are welcome.

Installing from source

  1. First, make sure the following dependencies are met:

    • Setuptools (pip3 install setuptools)
    • PyYAML (pip3 install pyyaml)
    • cachetools (pip3 install cachetools)
    • For hashed password support: Passlib >= 1.7.0 (pip3 install passlib)
    • For Unicode support in Relay: unidecode (pip3 install Unidecode)
    • For extended PID file tracking (i.e. removing stale PID files after a crash): psutil (pip3 install psutil)

  2. Clone the repository: git clone https://github.com/jlu5/PyLink && cd PyLink

  3. Pick your branch.

    • By default you’ll be on the master branch, which contains the latest stable code. This branch is recommended for production networks that don’t require new features or intensive bug fixes as they are developed.
    • The devel branch is where active development goes, and it can be accessed by running git checkout devel in your Git tree.

  4. Install PyLink using python3 setup.py install (global install) or python3 setup.py install --user (local install)

    • Note: --user is a literal string; do not replace it with your username.
    • Whenever you switch branches or update PyLink’s sources via git pull, you will need to re-run this command for changes to apply!

Installing via PyPI (stable branch only)

  1. Make sure you’re running the right pip command: on most distros, pip for Python 3 uses the command pip3.

  2. Run pip3 install pylinkirc to download and install PyLink. pip will automatically resolve dependencies.

  3. Download or copy https://github.com/jlu5/PyLink/blob/master/example-conf.yml for an example configuration.

Configuration

  1. Rename example-conf.yml to pylink.yml (or a similarly named .yml file) and configure your instance there.

  2. Run pylink from the command line. PyLink will load its configuration from pylink.yml by default, but you can override this by running pylink with a config argument (e.g. pylink mynet.yml).

Supported IRCds

Primary support

These IRCds (in alphabetical order) are frequently tested and well supported. If any issues occur, please file a bug on the issue tracker.

  • InspIRCd (2.0 - 3.x) - module inspircd
    • Set the target_version option to insp3 to target InspIRCd 3.x, or insp20 to target InspIRCd 2.0 (currently the default).
    • For vHost setting to work, m_chghost.so must be loaded. For ident and realname changing support, m_chgident.so and m_chgname.so must be loaded respectively.
    • Supported channel, user, and prefix modes are negotiated on connect, but hotloading modules that change these is not supported. After changing module configuration, it is recommended to SQUIT PyLink to force a protocol renegotiation.
  • Nefarious IRCu (2.0.0+) - module p10
    • Note: Both account cloaks (user and oper) and hashed IP cloaks are optionally supported (HOST_HIDING_STYLE settings 0 to 3). Make sure you configure PyLink to match your IRCd settings.
  • UnrealIRCd (4.2.x - 5.0.x) - module unreal
    • Supported channel, user, and prefix modes are negotiated on connect, but hotloading modules that change these is not supported. After changing module configuration, it is recommended to SQUIT PyLink to force a protocol renegotiation.

Extended support

Support for these IRCds exist, but are not tested as frequently and thoroughly. Bugs should be filed if there are any issues, though they may not always be fixed in a timely fashion.

  • charybdis (3.5+) - module ts6
    • For KLINE support to work, a shared{} block should be added for PyLink on all servers.
  • ChatIRCd (1.2.x / git master) - module ts6
    • For KLINE support to work, a shared{} block should be added for PyLink on all servers.
  • juno-ircd (13.x / ava) - module ts6 (see configuration example)
  • ngIRCd (24+) - module ngircd
    • For GLINEs to propagate, the AllowRemoteOper option must be enabled in ngIRCd.
    • + (modeless) channels are not supported, and should be disabled for PyLink to function correctly.
    • For use with Relay, the CloakHostModeX setting will work fine but CloakHost and CloakUserToNick are not supported.

Legacy extended support

Support for these IRCds was added at some point but is no longer actively maintained, either due to inactive upstream development or a perceived lack of interest. We recommend migrating to an IRCd in the above two sections.

  • beware-ircd (1.6.3) - module p10
    • Because bircd disallows BURST after ENDBURST for regular servers, U-lines are required for all PyLink servers. Fortunately, wildcards are supported in U-lines, so you can add something along the lines of U:<your pylink server>: and U:*.relay: (adjust accordingly for your relay server suffix).
    • Use ircd: snircd as the target IRCd.
    • Halfops, sethost (+h), and account-based cloaking (VHostStyle=1) are supported. Crypted IPs and static hosts (VHostStyle 2 and 3) are NOT.
  • Elemental-IRCd (6.6.x / git master) - module ts6
    • For KLINE support to work, a shared{} block should be added for PyLink on all servers.
  • IRCd-Hybrid (8.2.x / svn trunk) - module hybrid
    • For host changing support and optimal functionality, a service{} block / U-line should be added for PyLink on every IRCd across your network.
    • For KLINE support to work, a shared{} block should also be added for PyLink on all servers.
  • ircd-ratbox (3.x) - module ts6
    • Host changing is not supported.
    • On ircd-ratbox, all known IPs of users will be shown in /whois, even if the client is e.g. a cloaked relay client. If you’re paranoid about this, turn off Relay IP forwarding on the ratbox network(s).
    • For KLINE support to work, a shared{} block should be added for PyLink on all servers.
  • IRCu (u2.10.12.16+) - module p10
    • Host changing (changehost, relay) is not supported.
  • snircd (1.3.x+) - module p10
    • Outbound host changing (i.e. for the changehost plugin) is not supported.

Clientbot

PyLink supports connecting to IRCds as a relay bot and forwarding users back as virtual clients, similar to Janus’ Clientbot. This can be useful if the IRCd a network used isn’t supported, or if you want to relay certain channels without fully linking with a network.

For Relay to work properly with Clientbot, be sure to load the relay_clientbot plugin in conjunction with relay.