Merge branch 'release/2.3.0' into 'stable'
[akkoma] / docs / installation / alpine_linux_en.md
1 # Installing on Alpine Linux
2 ## Installation
3
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.
5
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.
7
8 ### Required packages
9
10 * `postgresql`
11 * `elixir`
12 * `erlang`
13 * `erlang-parsetools`
14 * `erlang-xmerl`
15 * `git`
16 * `file-dev`
17 * Development Tools
18 * `cmake`
19
20 #### Optional packages used in this guide
21
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)
24 * `ImageMagick`
25 * `ffmpeg`
26 * `exiftool`
27
28 ### Prepare the system
29
30 * 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:
31
32 ```shell
33 awk 'NR==2' /etc/apk/repositories | sed 's/main/community/' | tee -a /etc/apk/repositories
34 ```
35
36 * Then update the system, if not already done:
37
38 ```shell
39 sudo apk update
40 sudo apk upgrade
41 ```
42
43 * Install some tools, which are needed later:
44
45 ```shell
46 sudo apk add git build-base cmake file-dev
47 ```
48
49 ### Install Elixir and Erlang
50
51 * Install Erlang and Elixir:
52
53 ```shell
54 sudo apk add erlang erlang-runtime-tools erlang-xmerl elixir
55 ```
56
57 * Install `erlang-eldap` if you want to enable ldap authenticator
58
59 ```shell
60 sudo apk add erlang-eldap
61 ```
62
63 ### Install PostgreSQL
64
65 * Install Postgresql server:
66
67 ```shell
68 sudo apk add postgresql postgresql-contrib
69 ```
70
71 * Initialize database:
72
73 ```shell
74 sudo /etc/init.d/postgresql start
75 ```
76
77 * Enable and start postgresql server:
78
79 ```shell
80 sudo rc-update add postgresql
81 ```
82
83 ### Install media / graphics packages (optional, see [`docs/installation/optional/media_graphics_packages.md`](../installation/optional/media_graphics_packages.md))
84
85 ```shell
86 sudo apk add ffmpeg imagemagick exiftool
87 ```
88
89 ### Install PleromaBE
90
91 * Add a new system user for the Pleroma service:
92
93 ```shell
94 sudo addgroup pleroma
95 sudo adduser -S -s /bin/false -h /opt/pleroma -H -G pleroma pleroma
96 ```
97
98 **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.
99
100 * Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
101
102 ```shell
103 sudo mkdir -p /opt/pleroma
104 sudo chown -R pleroma:pleroma /opt/pleroma
105 sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma
106 ```
107
108 * Change to the new directory:
109
110 ```shell
111 cd /opt/pleroma
112 ```
113
114 * Install the dependencies for Pleroma and answer with `yes` if it asks you to install `Hex`:
115
116 ```shell
117 sudo -Hu pleroma mix deps.get
118 ```
119
120 * Generate the configuration: `sudo -Hu pleroma mix pleroma.instance gen`
121 * Answer with `yes` if it asks you to install `rebar3`.
122 * This may take some time, because parts of pleroma get compiled first.
123 * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.
124
125 * 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):
126
127 ```shell
128 sudo -Hu pleroma mv config/{generated_config.exs,prod.secret.exs}
129 ```
130
131 * The previous command creates also the file `config/setup_db.psql`, with which you can create the database:
132
133 ```shell
134 sudo -Hu postgres psql -f config/setup_db.psql
135 ```
136
137 * Now run the database migration:
138
139 ```shell
140 sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
141 ```
142
143 * Now you can start Pleroma already
144
145 ```shell
146 sudo -Hu pleroma MIX_ENV=prod mix phx.server
147 ```
148
149 ### Finalize installation
150
151 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.
152
153 #### Nginx
154
155 * Install nginx, if not already done:
156
157 ```shell
158 sudo apk add nginx
159 ```
160
161 * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
162
163 ```shell
164 sudo apk add certbot
165 ```
166
167 and then set it up:
168
169 ```shell
170 sudo mkdir -p /var/lib/letsencrypt/
171 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
172 ```
173
174 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).
175
176 * Copy the example nginx configuration to the nginx folder
177
178 ```shell
179 sudo cp /opt/pleroma/installation/pleroma.nginx /etc/nginx/conf.d/pleroma.conf
180 ```
181
182 * 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).
183
184 ```
185 server {
186 server_name your.domain;
187 listen 80;
188 ...
189 }
190
191 server {
192 server_name your.domain;
193 listen 443 ssl http2;
194 ...
195 ssl_trusted_certificate /etc/letsencrypt/live/your.domain/chain.pem;
196 ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
197 ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
198 ...
199 }
200 ```
201
202 * Enable and start nginx:
203
204 ```shell
205 sudo rc-update add nginx
206 sudo service nginx start
207 ```
208
209 If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
210
211 ```shell
212 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
213 ```
214
215 #### OpenRC service
216
217 * Copy example service file:
218
219 ```shell
220 sudo cp /opt/pleroma/installation/init.d/pleroma /etc/init.d/pleroma
221 ```
222
223 * Make sure to start it during the boot
224
225 ```shell
226 sudo rc-update add pleroma
227 ```
228
229 #### Create your first user
230
231 If your instance is up and running, you can create your first user with administrative rights with the following task:
232
233 ```shell
234 sudo -Hu pleroma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
235 ```
236
237 #### Further reading
238
239 {! backend/installation/further_reading.include !}
240
241 ## Questions
242
243 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**.