1 # Installing on Alpine Linux
4 This guide is a step-by-step installation guide for Alpine Linux. It also assumes that you have administrative rights, either as root or a user with [sudo permissions](https://www.linode.com/docs/tools-reference/custom-kernels-distros/install-alpine-linux-on-your-linode/#configuration). If you want to run this guide with root, ignore the `sudo` at the beginning of the lines, unless it calls a user like `sudo -Hu pleroma`; in this case, use `su -l <username> -s $SHELL -c 'command'` instead.
16 #### Optional packages used in this guide
18 * `nginx` (preferred, example configs for other reverse proxies can be found in the repo)
19 * `certbot` (or any other ACME client for Let’s Encrypt certificates)
21 ### Prepare the system
23 * First make sure to have the community repository enabled:
26 echo "https://nl.alpinelinux.org/alpine/latest-stable/community" | sudo tee -a /etc/apk/repository
29 * Then update the system, if not already done:
36 * Install some tools, which are needed later:
39 sudo apk add git build-base
42 ### Install Elixir and Erlang
44 * Install Erlang and Elixir:
47 sudo apk add erlang erlang-runtime-tools erlang-xmerl elixir
50 * Install `erlang-eldap` if you want to enable ldap authenticator
53 sudo apk add erlang-eldap
55 ### Install PostgreSQL
57 * Install Postgresql server:
60 sudo apk add postgresql postgresql-contrib
63 * Initialize database:
66 sudo /etc/init.d/postgresql start
69 * Enable and start postgresql server:
72 sudo rc-update add postgresql
77 * Add a new system user for the Pleroma service:
80 sudo adduser -S -s /bin/false -h /opt/pleroma -H pleroma
83 **Note**: To execute a single command as the Pleroma system user, use `sudo -Hu pleroma command`. You can also switch to a shell by using `sudo -Hu pleroma $SHELL`. If you don’t have and want `sudo` on your system, you can use `su` as root user (UID 0) for a single command by using `su -l pleroma -s $SHELL -c 'command'` and `su -l pleroma -s $SHELL` for starting a shell.
85 * Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
88 sudo mkdir -p /opt/pleroma
89 sudo chown -R pleroma:pleroma /opt/pleroma
90 sudo -Hu pleroma git clone https://git.pleroma.social/pleroma/pleroma /opt/pleroma
93 * Change to the new directory:
99 * Install the dependencies for Pleroma and answer with `yes` if it asks you to install `Hex`:
102 sudo -Hu pleroma mix deps.get
105 * Generate the configuration: `sudo -Hu pleroma mix pleroma.instance gen`
106 * Answer with `yes` if it asks you to install `rebar3`.
107 * This may take some time, because parts of pleroma get compiled first.
108 * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.
110 * Check the configuration and if all looks right, rename it, so Pleroma will load it (`prod.secret.exs` for productive instance, `dev.secret.exs` for development instances):
113 mv config/{generated_config.exs,prod.secret.exs}
116 * The previous command creates also the file `config/setup_db.psql`, with which you can create the database:
119 sudo -Hu postgres psql -f config/setup_db.psql
122 * Now run the database migration:
125 sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
128 * Now you can start Pleroma already
131 sudo -Hu pleroma MIX_ENV=prod mix phx.server
134 ### Finalize installation
136 If you want to open your newly installed instance to the world, you should run nginx or some other webserver/proxy in front of Pleroma and you should consider to create an OpenRC service file for Pleroma.
140 * Install nginx, if not already done:
146 * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
155 sudo mkdir -p /var/lib/letsencrypt/
156 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
159 If that doesn’t work, make sure, that nginx is not already running. If it still doesn’t work, try setting up nginx first (change ssl “on” to “off” and try again).
161 * Copy the example nginx configuration to the nginx folder
164 sudo cp /opt/pleroma/installation/pleroma.nginx /etc/nginx/conf.d/pleroma.conf
167 * Before starting nginx edit the configuration and change it to your needs (e.g. change servername, change cert paths)
168 * Enable and start nginx:
171 sudo rc-update add nginx
172 sudo service nginx start
175 If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
178 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
183 * Copy example service file:
186 sudo cp /opt/pleroma/installation/init.d/pleroma /etc/init.d/pleroma
189 * Make sure to start it during the boot
192 sudo rc-update add pleroma
195 #### Create your first user
197 If your instance is up and running, you can create your first user with administrative rights with the following task:
200 sudo -Hu pleroma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
205 * [Admin tasks](Admin tasks)
206 * [Backup your instance](Backup-your-instance)
207 * [Configuration tips](General tips for customizing pleroma fe)
208 * [Hardening your instance](Hardening-your-instance)
209 * [How to activate mediaproxy](How-to-activate-mediaproxy)
210 * [Small Pleroma-FE customizations](Small customizations)
211 * [Updating your instance](Updating-your-instance)
215 Questions about the installation or didn’t it work as it should be, ask in [#pleroma:matrix.org](https://matrix.heldscal.la/#/room/#freenode_#pleroma:matrix.org) or IRC Channel **#pleroma** on **Freenode**.