Fork of Pleroma with site-specific changes and feature branches https://git.pleroma.social/pleroma/pleroma
Go to file
Haelwenn f34e22bba2 Merge branch 'feat/expose_email_to_self' into 'develop'
Expose user email address to user/owner; not publicly.

See merge request pleroma/pleroma!3412
2021-05-26 18:04:23 +00:00
.gitlab
benchmarks
config Switch from the deprecated "use Mix.config" to "import Config" 2021-05-20 14:02:58 -05:00
docs Merge remote-tracking branch 'pleroma/develop' into optional-config 2021-05-16 12:27:29 -05:00
installation
lib Expose user email address to user/owner; not publicly. 2021-05-20 12:50:43 -05:00
priv Merge remote-tracking branch 'upstream/develop' into earmark 2021-04-30 13:17:03 -05:00
rel
restarter
test Merge branch 'feat/expose_email_to_self' into 'develop' 2021-05-26 18:04:23 +00:00
uploads
.buildpacks
.credo.exs
.dockerignore
.formatter.exs
.gitattributes
.gitignore Vi and emacs temp files 2021-02-24 12:11:50 -06:00
.gitlab-ci.yml CI: Purge pleroma build directory between runs 2021-04-29 13:15:48 -05:00
.mailmap
AGPL-3
CC-BY-4.0
CC-BY-SA-4.0
CHANGELOG.md Expose user email address to user/owner; not publicly. 2021-05-20 12:50:43 -05:00
COPYING
coveralls.json
docker-entrypoint.sh
Dockerfile
elixir_buildpack.config
mix.exs Merge remote-tracking branch 'upstream/attachment-meta' into blurhash 2021-05-14 09:09:32 -05:00
mix.lock Merge remote-tracking branch 'upstream/attachment-meta' into blurhash 2021-05-14 09:09:32 -05:00
Procfile
README.md
SECURITY.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

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 not packaged by any OS/Distros, but if you want to package it for one, 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 dont 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 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