elestio/pleroma
Pleroma, verified and packaged by Elestio
7.1K
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.
Deploy a fully managed pleroma on elest.io if you are interested in exploring a decentralized and community-oriented approach to online content.
You can deploy it easily with the following command:
git clone https://github.com/elestio-examples/pleroma.git
Copy the .env file from tests folder to the project directory
cp ./tests/.env ./.env
Edit the .env file with your own values.
Run the project with the following command
docker-compose up -d
You can access the Web UI at: http://your-domain:3226
Here are some example snippets to help you get started creating a container.
version: "3.3"
services: pleroma: user: 0:0 image: elestio/pleroma:${SOFTWARE_VERSION_TAG} restart: always hostname: "pleroma" labels: - "org.label-schema.group=pleroma" env_file: ./.env depends_on: - pleroma-db ports: - "172.17.0.1:3226:4000" volumes: - ./storage/pleroma//uploads:/data/uploads - ./storage/pleroma//static:/data/static - ./config.exs:/data/config.exs
pleroma-db:
image: elestio/postgres:15
restart: always
hostname: "pleroma-db"
labels:
- "com.centurylinklabs.watchtower.enable=False"
- "org.label-schema.group=pleroma"
env_file: ./.env
ports:
- "172.17.0.1:57249:5432"
volumes:
- ./storage/pleroma-db/pgdata:/var/lib/postgresql/data
pgadmin4:
image: dpage/pgadmin4:latest
restart: always
environment:
PGADMIN_DEFAULT_EMAIL: ${ADMIN_EMAIL}
PGADMIN_DEFAULT_PASSWORD: ${ADMIN_PASSWORD}
PGADMIN_LISTEN_PORT: 8080
ports:
- "172.17.0.1:55871:8080"
volumes:
- ./servers.json:/pgadmin4/servers.json
Variable | Value (example) |
---|---|
SOFTWARE_VERSION_TAG | latest |
POSTGRES_PASSWORD | password |
POSTGRES_USER | user-name |
POSTGRES_DB | db-name |
ADMIN_EMAIL | your-email |
ADMIN_PASSWORD | your-pass |
DB_USER | user-name |
DB_PASS | db-name |
DB_HOST | db-host |
DB_PORT | 5432 |
DB_NAME | pleroma |
INSTANCE_NAME | Pleroma |
DOMAIN | db-name |
The Elestio Pleroma Docker image sends the container logs to stdout. To view the logs, you can use the following command:
docker-compose logs -f
To stop the stack you can use the following command:
docker-compose down
To make backup and restore operations easier, we are using folder volume mounts. You can simply stop your stack with docker-compose down, then backup all the files and subfolders in the folder near the docker-compose.yml file.
Creating a ZIP Archive For example, if you want to create a ZIP archive, navigate to the folder where you have your docker-compose.yml file and use this command:
zip -r myarchive.zip .
Restoring from ZIP Archive To restore from a ZIP archive, unzip the archive into the original folder using the following command:
unzip myarchive.zip -d /path/to/original/folder
Starting Your Stack Once your backup is complete, you can start your stack again with the following command:
docker-compose up -d
That's it! With these simple steps, you can easily backup and restore your data volumes using Docker Compose.
docker pull elestio/pleroma