a1batross
/
pleroma
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity
Pleroma instance running on expired.mentality.rip https://expired.mentality.rip
8,676 Commits 3 Branches 0 Tags 244 MiB
JavaScript 71.8%
Elixir 26.6%
HTML 0.9%
Gettext Catalog 0.5%
Go to file
rinpatch 80bc8c2cc9 Revert "Set better Cache-Control header for static content" 
On furher investigation it seems like all that did was cause unintuitive
behavior. The emoji request flood that was the reason for introducing it
isn't really that big of a deal either, since Plug.Static only needs to
read file modification time and size to determine the ETag.

Closes #1613
 		2020-03-15 16:59:39 +03:00
benchmarks Add benchmark of any/all tag options 2020-01-20 12:19:15 +01:00
config Merge branch 'prepared-statements-settings' into 'develop' 2020-03-02 17:00:04 +00:00
docs Merge branch 'docs/new_user' into 'develop' 2020-03-15 16:59:20 +03:00
installation Update Copyrights 2020-03-03 16:44:49 -06:00
lib Revert "Set better Cache-Control header for static content" 2020-03-15 16:59:39 +03:00
priv static-fe.css: Restore from before a65ee8ea 2020-03-15 16:55:00 +03:00
rel OTP releases: only set name and distribution type if not set already 2019-11-22 19:58:39 +03:00
restarter wait in mix task while pleroma is rebooted 2020-03-07 16:02:55 +03:00
test Revert "Set better Cache-Control header for static content" 2020-03-15 16:59:39 +03: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 Update docker release / stable jobs 2020-01-15 17:25:33 -05: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 Merge branch 'fix/signup-without-email' into 'develop' 2020-03-15 16:58:51 +03:00
COPYING pleroma-fox-tan-shy.png: Add another version of pleroma-tan 2019-05-12 05:09:15 +02:00
Dockerfile Update Dockerfile with labels. Update gitlab-ci for registry usage 2020-01-10 14:09:14 -05: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
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 mix.exs: bump version to 2.0.1 2020-03-15 16:54:27 +03:00
mix.lock ActivityPub actions & side-effects in transaction 2020-03-01 12:01:39 +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

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 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 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.

Documentation

Community Channels