A versatile IRC bouncer.
## Requirements
- Python3.5
- Pip3.5
## Setup
- Install dependencies:
``[sudo] pip3.5 install -r requirements.txt``
- Copy and extend
``ircb/config/default_settings.py``, as needed, to a custom location. say, ``/etc/ircb/settings.py``.
- [OPTIONAL] ``export IRCB_SETTINGS=<path to your custom settings file>``
- Install the project as a development dep
``python3.5 setup.py develop``
## Setup for development
- Install system dependencies:
`` sudo dnf install python3-devel openssl-devel redis``
`` sudo pip install virtualenvwrapper``
- Make `python3` virtualenv:
``mkvirtualenv --python=/usr/bin/python3 python3``
- Activate virtualenv:
``workon python3``
- Install dependencies:
``pip3 install -r requirements.txt``
- Install the project as development dep:
``python3.5 setup.py develop``
- Make sure `REDIS` is running:
``sudo systemctl start redis.service``
- Now, you need to run ``ircb stores``:
``ircb run stores``
Continue with `` Setting up data``
## Setting up data
- Creating a user:
```
ircb users create USERNAME EMAIL [PASSWORD]
```
- Creating a network for a user:
```
ircb networks create USER NETWORK_NAME HOST PORT NICK
```
You'll get an access token as an output of the above. Use this as
**server password** when configuring your IRC client to connect to ``ircb``.
## Running the app
### Quickstart
```
sudo ircb run allinone
```
Note: If you are using virtualenv `sudo` will not work this way, you need to
run:
```
sudo ~/.virtualenvs/python3/bin/ircb run allinone
```
### Advanced
You can run the various components of ``ircb``: ``stores``, ``bouncers`` as
different processes.
- Run stores as a different process: ``ircb run stores``
- Run bouncer: ``ircb run bouncer``
- Run web server: ``ircb run web``
- Run identd server: ``sudo ircb run identd``
## Connecting for IRC client
Now, you should be able to connect to ``ircb`` from your IRC client at:
- host/port: ``localhost/9000``
- server password: ``<your network access token>``
- IRC client should have the following settings enabled:
* Use SSL for all server on this network
* Accept invalid SSL certificate
### Configure HexChat
- Go to HexChat -> Network List
- Change the nick to the nick you have given while configuring network
- Under ``Network`` Click `Add` and name the server ``ircb``
- Click on `Edit` then `Add` and type `localhost/9000`
- Under ``Server`` tab check the ``SSL`` option mentioned above
- Enter the ``Server Password`` in `Password` field
- Close the dialog box and then connect to the network
Note: In case the problem persist try to ``restart`` ircb server
Metadata
Release files for ircb 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ircb-0.3.0.tar.gz | 34.8 kB | Without provenance | Details for ircb-0.3.0.tar.gz |
Release files / ircb-0.3.0.tar.gz
| Download URL | ircb-0.3.0.tar.gz |
|---|---|
| Size | 34.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f4bba4ec8b5514d9151843cbbff2fa8151f111b4a71d211a68f0d5a14c1a65c
|
|
BLAKE2b-256 checksum How to use checksums |
eac80ec7389ce72e1d3f63e6d0c5e00a1ed5bf09918be954870efb60a598eb62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ircb 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.