30ee64c0105e0b116c53eed5068239e65cff9cf1
[akkoma] / docs / installation / debian_based_en.md
1 # Installing on Debian Based Distributions
2 ## Installation
3
4 This guide will assume you are on Debian Stretch. This guide should also work with Ubuntu 16.04 and 18.04. It also assumes that you have administrative rights, either as root or a user with [sudo permissions](https://www.digitalocean.com/community/tutorials/how-to-add-delete-and-grant-sudo-privileges-to-users-on-a-debian-vps). 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 <username> -s $SHELL -c 'command'` instead.
5
6 ### Required packages
7
8 * `postgresql` (9.6+, Ubuntu 16.04 comes with 9.5, you can get a newer version from [here](https://www.postgresql.org/download/linux/ubuntu/))
9 * `postgresql-contrib` (9.6+, same situtation as above)
10 * `elixir` (1.8+, Follow the guide to install from the Erlang Solutions repo or use [asdf](https://github.com/asdf-vm/asdf) as the pleroma user)
11 * `erlang-dev`
12 * `erlang-nox`
13 * `git`
14 * `build-essential`
15 * `cmake`
16 * `ffmpeg`
17 * `ImageMagick`
18
19 #### Optional packages used in this guide
20
21 * `nginx` (preferred, example configs for other reverse proxies can be found in the repo)
22 * `certbot` (or any other ACME client for Let’s Encrypt certificates)
23
24 ### Prepare the system
25
26 * First update the system, if not already done:
27
28 ```shell
29 sudo apt update
30 sudo apt full-upgrade
31 ```
32
33 * Install some of the above mentioned programs:
34
35 ```shell
36 sudo apt install git build-essential postgresql postgresql-contrib cmake ffmpeg imagemagick
37 ```
38
39 ### Install Elixir and Erlang
40
41 * Download and add the Erlang repository:
42
43 ```shell
44 wget -P /tmp/ https://packages.erlang-solutions.com/erlang-solutions_2.0_all.deb
45 sudo dpkg -i /tmp/erlang-solutions_2.0_all.deb
46 ```
47
48 * Install Elixir and Erlang:
49
50 ```shell
51 sudo apt update
52 sudo apt install elixir erlang-dev erlang-nox
53 ```
54
55 ### Install PleromaBE
56
57 * Add a new system user for the Pleroma service:
58
59 ```shell
60 sudo useradd -r -s /bin/false -m -d /var/lib/pleroma -U pleroma
61 ```
62
63 **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.
64
65 * Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
66
67 ```shell
68 sudo mkdir -p /opt/pleroma
69 sudo chown -R pleroma:pleroma /opt/pleroma
70 sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma
71 ```
72
73 * Change to the new directory:
74
75 ```shell
76 cd /opt/pleroma
77 ```
78
79 * Install the dependencies for Pleroma and answer with `yes` if it asks you to install `Hex`:
80
81 ```shell
82 sudo -Hu pleroma mix deps.get
83 ```
84
85 * Generate the configuration: `sudo -Hu pleroma mix pleroma.instance gen`
86 * Answer with `yes` if it asks you to install `rebar3`.
87 * This may take some time, because parts of pleroma get compiled first.
88 * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.
89
90 * 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):
91
92 ```shell
93 mv config/{generated_config.exs,prod.secret.exs}
94 ```
95
96 * The previous command creates also the file `config/setup_db.psql`, with which you can create the database:
97
98 ```shell
99 sudo -Hu postgres psql -f config/setup_db.psql
100 ```
101
102 * Now run the database migration:
103
104 ```shell
105 sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
106 ```
107
108 * Now you can start Pleroma already
109
110 ```shell
111 sudo -Hu pleroma MIX_ENV=prod mix phx.server
112 ```
113
114 ### Finalize installation
115
116 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 a systemd service file for Pleroma.
117
118 #### Nginx
119
120 * Install nginx, if not already done:
121
122 ```shell
123 sudo apt install nginx
124 ```
125
126 * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
127
128 ```shell
129 sudo apt install certbot
130 ```
131
132 and then set it up:
133
134 ```shell
135 sudo mkdir -p /var/lib/letsencrypt/
136 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
137 ```
138
139 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).
140
141 ---
142
143 * Copy the example nginx configuration and activate it:
144
145 ```shell
146 sudo cp /opt/pleroma/installation/pleroma.nginx /etc/nginx/sites-available/pleroma.nginx
147 sudo ln -s /etc/nginx/sites-available/pleroma.nginx /etc/nginx/sites-enabled/pleroma.nginx
148 ```
149
150 * Before starting nginx edit the configuration and change it to your needs (e.g. change servername, change cert paths)
151 * Enable and start nginx:
152
153 ```shell
154 sudo systemctl enable --now nginx.service
155 ```
156
157 If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
158
159 ```shell
160 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
161 ```
162
163 #### Other webserver/proxies
164
165 You can find example configurations for them in `/opt/pleroma/installation/`.
166
167 #### Systemd service
168
169 * Copy example service file
170
171 ```shell
172 sudo cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
173 ```
174
175 * Edit the service file and make sure that all paths fit your installation
176 * Enable and start `pleroma.service`:
177
178 ```shell
179 sudo systemctl enable --now pleroma.service
180 ```
181
182 #### Create your first user
183
184 If your instance is up and running, you can create your first user with administrative rights with the following task:
185
186 ```shell
187 sudo -Hu pleroma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
188 ```
189
190 #### Further reading
191
192 {! backend/installation/further_reading.include !}
193
194 ## Questions
195
196 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**.