Page MenuHomePhorge

No OneTemporary

Authored By
Unknown
Size
6 KB
Referenced Files
None
Subscribers
None
diff --git a/README.md b/README.md
index 7a05b9e48..a10910fef 100644
--- a/README.md
+++ b/README.md
@@ -1,54 +1,56 @@
<img src="https://git.pleroma.social/pleroma/pleroma/uploads/8cec84f5a084d887339f57deeb8a293e/pleroma-banner-vector-nopad-notext.svg" width="300px" />
## 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](https://docs.joinmastodon.org/api/guidelines/) with Pleroma extensions (see the API section on <https://docs-develop.pleroma.social>).
- [Client Applications for Pleroma](https://docs-develop.pleroma.social/backend/clients/)
## 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](https://docs-develop.pleroma.social/backend/installation/otp_en/).
### 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.
- [Alpine Linux](https://docs-develop.pleroma.social/backend/installation/alpine_linux_en/)
- [Arch Linux](https://docs-develop.pleroma.social/backend/installation/arch_linux_en/)
- [CentOS 7](https://docs-develop.pleroma.social/backend/installation/centos7_en/)
- [Debian-based](https://docs-develop.pleroma.social/backend/installation/debian_based_en/)
- [Debian-based (jp)](https://docs-develop.pleroma.social/backend/installation/debian_based_jp/)
- [FreeBSD](https://docs-develop.pleroma.social/backend/installation/freebsd_en/)
- [Gentoo Linux](https://docs-develop.pleroma.social/backend/installation/gentoo_en/)
- [NetBSD](https://docs-develop.pleroma.social/backend/installation/netbsd_en/)
- [OpenBSD](https://docs-develop.pleroma.social/backend/installation/openbsd_en/)
- [OpenBSD (fi)](https://docs-develop.pleroma.social/backend/installation/openbsd_fi/)
### 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](#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>.
+There is a docker image available via the GitLab registry at `git.pleroma.social:5050/pleroma/pleroma`. You can see the `docker-compose.example.yaml` file in this repository for an example on how to deploy it using `docker-compose` or `docker stack deploy`.
+
+For more information, you can take a look at <https://github.com/angristan/docker-pleroma> or <https://glitch.sh/sn0w/pleroma-docker>.
### Compilation Troubleshooting
If you ever encounter compilation issues during the updating of Pleroma, you can try these commands and see if they fix things:
- `mix deps.clean --all`
- `mix local.rebar`
- `mix local.hex`
- `rm -r _build`
If you are not developing Pleroma, it is better to use the OTP release, which comes with everything precompiled.
## 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>
diff --git a/docker-compose.example.yaml b/docker-compose.example.yaml
new file mode 100644
index 000000000..c9b91a250
--- /dev/null
+++ b/docker-compose.example.yaml
@@ -0,0 +1,56 @@
+# An example deployment configuration for docker-compose and docker stack deploy
+version: '3'
+services:
+ db:
+ # If you would like to use things like search extensions
+ # (as in https://docs.pleroma.social/backend/configuration/howto_search_cjk/ )
+ # it may be more appropriate to use a custom postgres image.
+ image: postgres:alpine
+ # Create the environment file as follows:
+ # POSTGRES_USER=pleroma
+ # POSTGRES_DB=pleroma
+ # POSTGRES_PASSWORD=some-randomly-generated-password
+ env_file: postgres.env
+ networks:
+ - internal
+ healthcheck:
+ test: ["CMD", "pg_isready", "-U", "pleroma"]
+ volumes:
+ # Replace /path/to/pleroma with where you would like to store data.
+ # For deployments using docker-compose, you can also just use `./`.
+ - /path/to/pleroma/postgres:/var/lib/postgresql/data
+ # For docker stack deploy: you may want to restrict where to run
+ # the database, as in most cases it is best to put db files on a local disk
+ # for performance and reliability.
+ #deploy:
+ # placement:
+ # constraints:
+ # - 'node.hostname==this-machine-just-for-dbs'
+
+ pleroma:
+ # This is the stable image from pleroma's registry.
+ # To use the image built from the develop branch, use
+ # git.pleroma.social:5050/pleroma/pleroma:latest instead.
+ image: git.pleroma.social:5050/pleroma/pleroma:latest-stable
+ depends_on:
+ - db
+ networks:
+ - internal
+ - external
+ ports:
+ - "4000:4000"
+ # Create the environment file as follows:
+ # DB_PASS=some-randomly-generated-password
+ # DB_HOST=db
+ # DB_NAME=pleroma
+ # DB_USER=pleroma
+ env_file: pleroma.env
+ volumes:
+ - /path/to/pleroma/pleroma-data/uploads:/var/lib/pleroma/uploads
+ - /path/to/pleroma/pleroma-data/static:/var/lib/pleroma/static
+ - /path/to/pleroma/pleroma-data/conf:/etc/pleroma
+
+networks:
+ internal:
+ internal: true
+ external:

File Metadata

Mime Type
text/x-diff
Expires
Sun, Nov 1, 8:31 AM (5 h, 21 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
1802872
Default Alt Text
(6 KB)

Event Timeline