hj/pleroma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
15,706 commits 2 branches 0 tags 243 MiB
Find a file
lain 52aadc09e9 Merge branch 'exile' into 'develop' 
Replace custom fifo implementation with Exile

See merge request pleroma/pleroma!4039
2024-01-22 16:49:30 +00:00
.gitlab
benchmarks
changelog.d Replace custom fifo implementation with Exile 2024-01-22 10:13:17 -05:00
ci Rename 1.15 image to include otp25, clarify test names 2024-01-21 04:10:20 +00:00
config Use config to control starting all HTTP pools in test env 2024-01-20 19:10:57 -05:00
docs Update API docs for my changes 2024-01-17 17:13:21 +01:00
installation
lib Replace custom fifo implementation with Exile 2024-01-22 10:13:17 -05:00
priv
rel
restarter
test Merge branch 'handle_object_fetch_failures' into 'develop' 2024-01-19 18:43:00 +00:00
tools
uploads
.buildpacks
.credo.exs
.dockerignore
.formatter.exs
.gitattributes
.gitignore
.gitlab-ci.yml Fix testing cache policy 2024-01-21 04:35:31 +00:00
.mailmap
.rgignore
AGPL-3
CC-BY-4.0
CC-BY-SA-4.0
CHANGELOG.md
COPYING
coveralls.json
docker-entrypoint.sh
Dockerfile
elixir_buildpack.config
mix.exs Replace custom fifo implementation with Exile 2024-01-22 10:13:17 -05:00
mix.lock Replace custom fifo implementation with Exile 2024-01-22 10:13:17 -05:00
Procfile
README.md
SECURITY.md

README.md

About

Pleroma 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. Pleroma will federate with all servers that implement ActivityPub, like Friendica, GNU Social, Hubzilla, Mastodon, Misskey, Peertube, and Pixelfed.

Pleroma is written in Elixir and uses PostgresSQL for data storage. It's efficient enough to be ran on low-power devices like Raspberry Pi (though we wouldn't recommend storing the database on the internal SD card ;) but can scale well when ran on more powerful hardware (albeit only single-node for now).

For clients it supports the Mastodon client API with Pleroma extensions (see the API section on https://docs-develop.pleroma.social).

Installation

OTP releases (Recommended)

If you are running Linux (glibc or musl) on x86/arm, the recommended way to install Pleroma 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 Pleroma from source.

OS/Distro packages

Currently Pleroma is packaged for YunoHost, NixOS, Gentoo through GURU and Archlinux through AUR. You may find more at https://repology.org/project/pleroma/versions.
If you want to package Pleroma for any OS/Distros, we can guide you through the process on our community channels. If you want to change default options in your Pleroma package, please discuss it with us first.

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.

Raspberry Pi

Community maintained Raspberry Pi image that you can flash and run Pleroma on your Raspberry Pi. Available here https://github.com/guysoft/PleromaPi.

Compilation Troubleshooting

If you ever encounter compilation issues during the updating of Pleroma, you can try these commands and see if they fix things:

  • mix deps.clean --all
  • mix local.rebar
  • mix local.hex
  • rm -r _build

If you are not developing Pleroma, it is better to use the OTP release, which comes with everything precompiled.

Documentation

Community Channels