Pleroma ActivityRelay
Go to file
Izalia Mae f98ca54ab7 various changes
* Add oauth login support
* Add `HttpError` class
* Add custom error handling
* Use `blib.Date` class for (de)serializing db timestamp values
* Add `db-maintenance` command
* Rework middleware route checking
* Fix fetching post data in api endpoints
2024-07-04 20:36:04 -04:00
docs update installation docs to replace git+http url with pypi package 2024-04-02 14:29:49 -04:00
installation properly detect if running via systemd 2024-03-27 11:48:05 -04:00
relay various changes 2024-07-04 20:36:04 -04:00
.gitignore change metadata name to ActivityRelay 2024-04-01 15:12:01 -04:00
dev.py ensure the relay can run on python >= 3.10 2024-07-03 00:59:59 -04:00
docker.sh Fix running via docker 2024-04-02 12:32:49 -04:00
Dockerfile Fix running via docker 2024-04-02 12:32:49 -04:00
LICENSE Initial commit 2018-08-10 18:36:17 +00:00
pyproject.toml ensure the relay can run on python >= 3.10 2024-07-03 00:59:59 -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
tox.ini convert setup.cfg to pyproject.toml 2024-04-01 15:38:29 -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