pch_xyz/relay
1
0
Fork 0
mirror of https://git.pleroma.social/pleroma/relay.git synced 2024-11-23 15:08:00 +00:00
Code Issues Packages Projects Releases Wiki Activity
Pleroma ActivityRelay
306 commits 3 branches 12 tags 2.2 MiB
Python 87.5%
Haml 7.6%
CSS 3.2%
Shell 1.2%
Dockerfile 0.5%
Go to file
Izalia Mae b0f838ec07 Merge branch 'sql' into 'master' 
Draft: switch database backend to sql

See merge request pleroma/relay!53
2024-01-27 05:59:17 +00:00
docs update docs for new commands and config file 2024-01-24 00:48:15 -05:00
installation update relay.service file to use run command 2024-01-23 22:04:07 -05:00
relay update tinysql and set min/max db connections per thread 2024-01-27 00:59:08 -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 actually fix python packaging this time 2024-01-22 06:39:12 -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 update tinysql and set min/max db connections per thread 2024-01-27 00:59:08 -05:00
relay.yaml.example use postgresql/sqlite for database backend 2024-01-22 05:32:16 -05:00
requirements.txt update tinysql and set min/max db connections per thread 2024-01-27 00:59:08 -05:00
setup.cfg move dev requirements to dev-requirements.txt and only use flake8 for checking unused imports 2024-01-23 21:51:17 -05:00
setup.py add packaging 2021-10-14 16:09:21 -04:00

README.md

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