Pleroma ActivityRelay
Go to file
2024-02-20 13:06:47 -05:00
docs update docs 2024-02-18 08:02:43 -05:00
installation update relay.service file to use run command 2024-01-23 22:04:07 -05:00
relay e 2024-02-19 23:52:03 -05:00
.gitignore use postgresql/sqlite for database backend 2024-01-22 05:32:16 -05:00
dev-requirements.txt move dev requirements to dev-requirements.txt and only use flake8 for checking unused imports 2024-01-23 21:51:17 -05: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
MANIFEST.in add swagger api docs 2024-02-16 20:25:50 -05:00
pyproject.toml add plugins to pylint 2024-01-23 21:54:05 -05:00
README.md Reorganize codebase 2022-05-06 07:04:51 +00:00
relay.spec fix running via pyinstaller bin 2024-02-16 21:05:12 -05:00
relay.yaml.example add database and redis caching 2024-01-31 21:23:45 -05:00
requirements.txt set barkshark-sql to 0.1.1 2024-02-20 13:06:47 -05:00
setup.cfg replace tinysql with barkshark-sql 2024-02-19 18:35:40 -05: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