|19ac2c74cf||4 years ago|
|custom.d||5 years ago|
|.dockerignore||4 years ago|
|.env.dist||4 years ago|
|.gitignore||4 years ago|
|Dockerfile||4 years ago|
|LICENSE||5 years ago|
|README.md||4 years ago|
|config.dist.exs||4 years ago|
|docker-compose.yml||4 years ago|
|entrypoint.sh||4 years ago|
|initdb.sql||5 years ago|
|pleroma.sh||4 years ago|
Pleroma is a selfhosted social network that uses OStatus/ActivityPub.
This repository dockerizes it for easier deployment.
#include <LICENSE> /* * This repository comes with ABSOLUTELY NO WARRANTY * * I am not responsible for burning servers, angry users, fedi drama, * thermonuclear war, or you getting fired because your boss saw your NSFW posts. * Please do some research if you have any concerns about included * features or the software used by this script ***before*** using it. * */
In the Wild
My own instance is managed by this script.
Take a look at hosted/pleroma if you get stuck or need some inspiration.
Does your instance use pleroma-docker?
Let me know and I'll add you to this list.
These docs assume that you have at least a basic understanding of the pleroma installation process and common docker commands.
If you have questions about Pleroma head over to https://docs-develop.pleroma.social/.
For help with docker check out https://docs.docker.com/.
For other problems related to this script, contact me or open an issue :)
- ~1GB of free HDD space
gitif you want smart build caches
dialogif you want to use
- Bash 4+
- Docker 18.06+ and docker-compose 1.22+
- Clone this repository
- Create a
- Configure a reverse-proxy
You can also use normal
docker-compose commands to maintain your setup.
The only command that you cannot use is
docker-compose build due to build caching.
All the pleroma options that you usually put into your
*.secret.exs now go into
.env stores config values that need to be known at orchestration/build time.
Documentation for the possible values is inside of that file.
./pleroma.sh build again and start the updated image with
You don't need to stop your pleroma server for either of those commands.
Pleroma maintenance is usually done with mix tasks.
You can run these tasks in your running pleroma server using
./pleroma.sh mix [task] [arguments...].
./pleroma.sh mix pleroma.user new sn0w ...
If you need to fix bigger problems you can also spawn a shell with
Add your customizations (and their folder structure) to
They will be copied into the right place when the container starts.
You can even replace/patch pleroma’s code with this, because the project is recompiled at startup if needed.
In general: Prepending
custom.d/ to pleroma’s customization guides should work all the time.
Check them out in the official pleroma wiki.
For example: A custom thumbnail now goes into
Works exactly like customization, but we have a neat little helper here.
./pleroma.sh mod [regex] to mod any file that ships with pleroma, without having to type the complete path.
My instance is up, how do I reach it?
To reach Gopher or SSH, just uncomment the port-forward in your
To reach HTTP you will have to configure a "reverse-proxy". Older versions of this script contained a huge amount of scripting to support all kinds of reverse-proxy setups. This newer version tries to focus only on providing good pleroma tooling. That makes the whole process a bit more manual, but also more flexible.
You can use Caddy, Traefik, Apache, nginx, or whatever else you come up with.
Just modify your
One example would be to add an nginx server to your
# ... proxy: image: nginx init: true restart: unless-stopped links: - server volumes: - ./my-nginx-config.conf:/etc/nginx/nginx.conf:ro ports: - "80:80" - "443:443"
Then take a look at the pleroma nginx example for hints about what to put into
Using apache would work in a very similar way (see Apache Docker Docs and the pleroma apache example).
The target that you proxy to is called
This will work automagically when the proxy also lives inside of docker.
If you need help with this, or if you think that this needs more documentation, please let me know.
Something that cofe.rocks uses is simple port-forwarding of the
server container to the host's
From there on, the natively installed nginx server acts as a proxy to the open internet.
You can take a look at this file and cofe's proxy config if that setup sounds interesting.
Thanks to Angristan and RX14 for their dockerfiles, which served as an inspiration for the early versions of this script.
The current version is based on the official wiki guides.
Thanks to all people who contributed to those.