where we keep the spc fork
Go to file
lain 801e668a97 ChatController: Add `last_read_id` option to mark_as_read. 2020-06-07 15:38:33 +02:00
.gitlab gitlab: create templates for bug reports and release MRs 2020-03-16 17:30:50 +03:00
benchmarks replies filtering for blocked domains 2020-06-02 09:00:10 +03:00
config Merge branch 'tagline' into 'develop' 2020-06-02 14:10:53 +00:00
docs Docs: Unify parameters in examples. 2020-06-06 10:35:38 +02:00
installation Apply suggestion to installation/nginx-cache-purge.sh.example 2020-05-20 04:12:21 +00:00
lib ChatController: Add `last_read_id` option to mark_as_read. 2020-06-07 15:38:33 +02:00
priv Chats: Change id to flake id. 2020-06-07 14:25:30 +02:00
rel OTP releases: only set name and distribution type if not set already 2019-11-22 19:58:39 +03:00
restarter Merge branch 'develop' into gun 2020-03-07 12:41:37 +03:00
test ChatController: Add `last_read_id` option to mark_as_read. 2020-06-07 15:38:33 +02:00
uploads fix issues with the uploads directory 2019-04-28 06:43:00 +02:00
.buildpacks CI: Add auto-deployment via dokku. 2019-05-31 10:55:35 +02:00
.credo.exs [Credo][CI] Add readability as it’s fixed 2019-03-13 04:26:56 +01:00
.dockerignore remove docs/ from .dockerignore 2019-11-20 00:09:07 +09:00
.formatter.exs HTML: Compile Scrubbers on boot 2019-12-08 20:35:41 +03:00
.gitattributes .gitattributes: use native support for elixir definitions 2020-02-17 13:27:28 +03:00
.gitignore ActivityPub actions & side-effects in transaction 2020-03-01 12:01:39 +03:00
.gitlab-ci.yml Give up for now and make gitlab retry failed jobs. 2020-05-12 15:02:37 +02:00
.mailmap add mailmap [ci skip] 2019-07-11 08:57:51 +00:00
AGPL-3 LICENSE → AGPL-3 2019-04-01 00:31:21 +02:00
CC-BY-SA-4.0 CC-BY-SA-4.0: Add a copy of the CC-BY-SA-4.0 license 2019-04-01 00:30:21 +02:00
CHANGELOG.md Changelog: Add chats to changelog. 2020-06-03 19:25:57 +02:00
COPYING Bump copyright dates. 2020-03-26 15:37:42 +01:00
Dockerfile Create OTP_VERSION file by `mix release` 2020-04-10 00:22:50 +09:00
Procfile CI: Add auto-deployment via dokku. 2019-05-31 10:55:35 +02:00
README.md readme: replace banner logo with the one using paths for text 2019-11-10 00:52:04 +03:00
coveralls.json tests for emoji mix task 2020-04-06 11:13:59 +03:00
docker-entrypoint.sh Create docker.exs and docker-entrypoint + round out Dockerfile 2019-08-03 00:21:54 -04:00
elixir_buildpack.config CI: Add auto-deployment via dokku. 2019-05-31 10:55:35 +02:00
mix.exs Update crypt library 2020-05-19 14:46:06 +03:00
mix.lock mix.lock: update hackney to 1.16.0 2020-05-30 00:18:17 +03:00

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

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.

Documentation

Community Channels