1 # Installing on Debian Based Distributions
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.
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)
17 #### Optional packages used in this guide
19 * `nginx` (preferred, example configs for other reverse proxies can be found in the repo)
20 * `certbot` (or any other ACME client for Let’s Encrypt certificates)
25 ### Prepare the system
27 * First update the system, if not already done:
34 * Install some of the above mentioned programs:
37 sudo apt install git build-essential postgresql postgresql-contrib cmake
40 ### Install Elixir and Erlang
42 * Download and add the Erlang repository:
45 wget -P /tmp/ https://packages.erlang-solutions.com/erlang-solutions_2.0_all.deb
46 sudo dpkg -i /tmp/erlang-solutions_2.0_all.deb
49 * Install Elixir and Erlang:
53 sudo apt install elixir erlang-dev erlang-nox
56 ### Optional packages: [`docs/installation/optional/media_graphics_packages.md`](docs/installation/optional/media_graphics_packages.md)
59 sudo apt install imagemagick ffmpeg libimage-exiftool-perl
64 * Add a new system user for the Pleroma service:
67 sudo useradd -r -s /bin/false -m -d /var/lib/pleroma -U pleroma
70 **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.
72 * Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
75 sudo mkdir -p /opt/pleroma
76 sudo chown -R pleroma:pleroma /opt/pleroma
77 sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma
80 * Change to the new directory:
86 * Install the dependencies for Pleroma and answer with `yes` if it asks you to install `Hex`:
89 sudo -Hu pleroma mix deps.get
92 * Generate the configuration: `sudo -Hu pleroma mix pleroma.instance gen`
93 * Answer with `yes` if it asks you to install `rebar3`.
94 * This may take some time, because parts of pleroma get compiled first.
95 * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.
97 * 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):
100 mv config/{generated_config.exs,prod.secret.exs}
103 * The previous command creates also the file `config/setup_db.psql`, with which you can create the database:
106 sudo -Hu postgres psql -f config/setup_db.psql
109 * Now run the database migration:
112 sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
115 * Now you can start Pleroma already
118 sudo -Hu pleroma MIX_ENV=prod mix phx.server
121 ### Finalize installation
123 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.
127 * Install nginx, if not already done:
130 sudo apt install nginx
133 * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
136 sudo apt install certbot
142 sudo mkdir -p /var/lib/letsencrypt/
143 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
146 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).
150 * Copy the example nginx configuration and activate it:
153 sudo cp /opt/pleroma/installation/pleroma.nginx /etc/nginx/sites-available/pleroma.nginx
154 sudo ln -s /etc/nginx/sites-available/pleroma.nginx /etc/nginx/sites-enabled/pleroma.nginx
157 * Before starting nginx edit the configuration and change it to your needs (e.g. change servername, change cert paths)
158 * Enable and start nginx:
161 sudo systemctl enable --now nginx.service
164 If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
167 sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
170 #### Other webserver/proxies
172 You can find example configurations for them in `/opt/pleroma/installation/`.
176 * Copy example service file
179 sudo cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
182 * Edit the service file and make sure that all paths fit your installation
183 * Enable and start `pleroma.service`:
186 sudo systemctl enable --now pleroma.service
189 #### Create your first user
191 If your instance is up and running, you can create your first user with administrative rights with the following task:
194 sudo -Hu pleroma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
199 {! backend/installation/further_reading.include !}
203 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**.