Pleroma ActivityRelay
Go to file
Izalia Mae cab8ca81c6 Merge branch 'dev' into 'main'
version 0.3.1

See merge request pleroma/relay!58
2024-03-31 22:24:06 +00:00
docs minor doc change 2024-03-13 18:52:22 -04:00
installation properly detect if running via systemd 2024-03-27 11:48:05 -04:00
relay ensure config key is formatted properly 2024-03-31 18:23:35 -04:00
.gitignore replace pylint with mypy and other minor changes 2024-03-13 17:43:57 -04:00
dev-requirements.txt use typing_extensions module for python < 3.11 2024-03-31 11:51:48 -04:00
docker.sh Reorganize codebase 2022-05-06 07:04:51 +00:00
Dockerfile Reorganize codebase 2022-05-06 07:04:51 +00:00
LICENSE Initial commit 2018-08-10 18:36:17 +00:00
pyproject.toml replace pylint with mypy and other minor changes 2024-03-13 17:43:57 -04:00
README.md Reorganize codebase 2022-05-06 07:04:51 +00:00
relay.yaml.example add database and redis caching 2024-01-31 21:23:45 -05:00
requirements.txt update aputils to 0.2.1 2024-03-31 11:52:05 -04:00
setup.cfg replace pylint with mypy and other minor changes 2024-03-13 17:43:57 -04:00
setup.py add packaging 2021-10-14 16:09:21 -04:00

ActivityRelay

A generic LitePub message relay.

Copyleft

ActivityRelay is copyrighted, but free software, licensed under the terms of the GNU Affero General Public License version 3 (AGPLv3) license. You can find a copy of it in this package as the LICENSE file.

Getting Started

Normally, you would direct your LitePub instance software to follow the LitePub actor found on the relay. In Pleroma this would be something like:

$ MIX_ENV=prod mix relay_follow https://your.relay.hostname/actor

Documentation

To install or manage your relay, check the documentation