c55301e760
I've noticed that sometimes when switching from develop to stable and back, develop fails to compile and rm -r ing the _build and deps dirs doesn't help at all. This is due to Admin API controller needing to generate JSON description of the config at compile time. Evaluating `config/description.exs` calls `Generator.list_modules_in_dir/2`, which in turn predicts the module names of files in the directory and tries to convert the predicted name to *existing* atoms. Sometimes the compiler will call that function before compiling the modules in the said directory, so the conversion will of course fail. This fixes it by removing the requirement of the atoms being existent. The function is not subjected to any untrusted user input so this should be safe. An ideal fix would be to block the compilation of docs before all modules are compiled and then get a list of compiled elixir modules under the namespace we want instead of directory hacks, but I have not been able to figure out how to do that. |
||
|---|---|---|
| benchmarks | ||
| config | ||
| docs | ||
| installation | ||
| lib | ||
| priv | ||
| rel | ||
| restarter | ||
| test | ||
| uploads | ||
| .buildpacks | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| AGPL-3 | ||
| CC-BY-SA-4.0 | ||
| CHANGELOG.md | ||
| COPYING | ||
| Dockerfile | ||
| Procfile | ||
| README.md | ||
| docker-entrypoint.sh | ||
| elixir_buildpack.config | ||
| mix.exs | ||
| mix.lock | ||
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.
- Debian-based
- Debian-based (jp)
- Alpine Linux
- Arch Linux
- Gentoo Linux
- NetBSD
- OpenBSD
- OpenBSD (fi)
- CentOS 7
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
- Latest Released revision: https://docs.pleroma.social
- Latest Git revision: https://docs-develop.pleroma.social
Community Channels
- IRC: #pleroma and #pleroma-dev on freenode, webchat is available at https://irc.pleroma.social
- Matrix: https://matrix.to/#/#freenode_#pleroma:matrix.org and https://matrix.to/#/#freenode_#pleroma-dev:matrix.org