Thomas Citharel
4d0a51221a
Some checks failed
ci/woodpecker/pr/woodpecker Pipeline failed
The header name was Report-To, not Reply-To. In any case, that's now being changed to the Reporting-Endpoints HTTP Response Header. https://w3c.github.io/reporting/#header https://github.com/w3c/reporting/issues/177 CanIUse says the Report-To header is still supported by current Chrome and friends. https://caniuse.com/mdn-http_headers_report-to It doesn't have any data for the Reporting-Endpoints HTTP header, but this article says Chrome 96 supports it. https://web.dev/reporting-api/ (Even though that's come out one year ago, that's not compatible with Network Error Logging which's still using the Report-To version of the API) Signed-off-by: Thomas Citharel <tcit@tcit.fr> |
||
---|---|---|
benchmarks | ||
ci | ||
config | ||
docker-resources | ||
docs | ||
installation | ||
lib | ||
priv | ||
rel | ||
restarter | ||
test | ||
uploads | ||
.buildpacks | ||
.credo.exs | ||
.dockerignore | ||
.formatter.exs | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.woodpecker.yml | ||
AGPL-3 | ||
CC-BY-4.0 | ||
CC-BY-SA-4.0 | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
COPYING | ||
coveralls.json | ||
docker-compose.yml | ||
docker-entrypoint.sh | ||
Dockerfile | ||
elixir_buildpack.config | ||
Makefile | ||
mix.exs | ||
mix.lock | ||
Procfile | ||
README.md | ||
SECURITY.md | ||
SIGNING_KEY.pub |
akkoma
a smallish microblogging platform, aka the cooler pleroma
About
This is a fork of Pleroma, which is a microblogging server software that can federate (= exchange messages with) other servers that support ActivityPub. What that means is that you can host a server for yourself or your friends and stay in control of your online identity, but still exchange messages with people on larger servers. Akkoma will federate with all servers that implement ActivityPub, like Friendica, GNU Social, Hubzilla, Mastodon, Misskey, Peertube, and Pixelfed.
Akkoma is written in Elixir and uses PostgresSQL for data storage.
For clients it supports the Mastodon client API with Pleroma extensions (see the API section on https://docs.akkoma.dev/stable/).
Installation
OTP releases (Recommended)
If you are running Linux (glibc or musl) on x86, the recommended way to install Akkoma is by using OTP releases. OTP releases are as close as you can get to binary releases with Erlang/Elixir. The release is self-contained, and provides everything needed to boot it. The installation instructions are available here.
From Source
If your platform is not supported, or you just want to be able to edit the source code easily, you may install Akkoma from source.
- Alpine Linux
- Arch Linux
- Debian-based
- Debian-based (jp)
- FreeBSD
- Gentoo Linux
- NetBSD
- OpenBSD
- OpenBSD (fi)
Docker
While we don’t provide docker files, other people have written very good ones. Take a look at https://github.com/angristan/docker-pleroma or https://glitch.sh/sn0w/pleroma-docker.
Compilation Troubleshooting
If you ever encounter compilation issues during the updating of Akkoma, you can try these commands and see if they fix things:
mix deps.clean --all
mix local.rebar
mix local.hex
rm -r _build