1 # Installing on Alpine Linux
4 This guide is a step-by-step installation guide for Alpine Linux. The instructions were verified against Alpine v3.10 standard image. You might miss additional dependencies if you use `netboot` instead.
6 It 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.
20 #### Optional packages used in this guide
22 * `nginx` (preferred, example configs for other reverse proxies can be found in the repo)
23 * `certbot` (or any other ACME client for Let’s Encrypt certificates)
25 ### Prepare the system
27 * The community repository must be enabled in `/etc/apk/repositories`. Depending on which version and mirror you use this looks like `http://alpine.42.fr/v3.10/community`. If you autogenerated the mirror during installation:
30 awk 'NR==2' /etc/apk/repositories | sed 's/main/community/' | tee -a /etc/apk/repositories
34 * Then update the system, if not already done:
41 * Install some tools, which are needed later:
44 sudo apk add git build-base cmake file-dev
47 ### Install Elixir and Erlang
49 * Install Erlang and Elixir:
52 sudo apk add erlang erlang-runtime-tools erlang-xmerl elixir
55 * Install `erlang-eldap` if you want to enable ldap authenticator
58 sudo apk add erlang-eldap
60 ### Install PostgreSQL
62 * Install Postgresql server:
65 sudo apk add postgresql postgresql-contrib
68 * Initialize database:
71 sudo /etc/init.d/postgresql start
74 * Enable and start postgresql server:
77 sudo rc-update add postgresql
82 * Add a new system user for the Pleroma service:
86 sudo adduser -S -s /bin/false -h /opt/pleroma -H -G pleroma pleroma
89 **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.
91 * Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
94 sudo mkdir -p /opt/pleroma
95 sudo chown -R pleroma:pleroma /opt/pleroma
96 sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma
99 * Change to the new directory:
105 * Install the dependencies for Pleroma and answer with `yes` if it asks you to install `Hex`:
108 sudo -Hu pleroma mix deps.get
111 * Generate the configuration: `sudo -Hu pleroma mix pleroma.instance gen`
112 * Answer with `yes` if it asks you to install `rebar3`.
113 * This may take some time, because parts of pleroma get compiled first.
114 * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.
116 * 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):
119 mv config/{generated_config.exs,prod.secret.exs}
122 * The previous command creates also the file `config/setup_db.psql`, with which you can create the database:
125 sudo -Hu postgres psql -f config/setup_db.psql
128 * Now run the database migration:
131 sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
134 * Now you can start Pleroma already
137 sudo -Hu pleroma MIX_ENV=prod mix phx.server
140 ### Finalize installation
142 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.
146 * Install nginx, if not already done:
152 * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
161 sudo mkdir -p /var/lib/letsencrypt/
162 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
165 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).
167 * Copy the example nginx configuration to the nginx folder
170 sudo cp /opt/pleroma/installation/pleroma.nginx /etc/nginx/conf.d/pleroma.conf
173 * Before starting nginx edit the configuration and change it to your needs. You must change change `server_name` and the paths to the certificates. You can use `nano` (install with `apk add nano` if missing).
177 server_name your.domain;
183 server_name your.domain;
184 listen 443 ssl http2;
186 ssl_trusted_certificate /etc/letsencrypt/live/your.domain/chain.pem;
187 ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
188 ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
193 * Enable and start nginx:
196 sudo rc-update add nginx
197 sudo service nginx start
200 If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
203 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
208 * Copy example service file:
211 sudo cp /opt/pleroma/installation/init.d/pleroma /etc/init.d/pleroma
214 * Make sure to start it during the boot
217 sudo rc-update add pleroma
220 #### Create your first user
222 If your instance is up and running, you can create your first user with administrative rights with the following task:
225 sudo -Hu pleroma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
230 {! backend/installation/further_reading.include !}
234 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**.