Fork of Pleroma with site-specific changes and feature branches https://git.pleroma.social/pleroma/pleroma
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

debian_based_en.md 6.4KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205
  1. # Installing on Debian Based Distributions
  2. ## Installation
  3. 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.
  4. ### Required packages
  5. * `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/))
  6. * `postgresql-contrib` (9.6+, same situtation as above)
  7. * `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)
  8. * `erlang-dev`
  9. * `erlang-nox`
  10. * `libmagic-dev`
  11. * `git`
  12. * `build-essential`
  13. * `cmake`
  14. #### Optional packages used in this guide
  15. * `nginx` (preferred, example configs for other reverse proxies can be found in the repo)
  16. * `certbot` (or any other ACME client for Let’s Encrypt certificates)
  17. * `ImageMagick`
  18. * `ffmpeg`
  19. * `exiftool`
  20. ### Prepare the system
  21. * First update the system, if not already done:
  22. ```shell
  23. sudo apt update
  24. sudo apt full-upgrade
  25. ```
  26. * Install some of the above mentioned programs:
  27. ```shell
  28. sudo apt install git build-essential postgresql postgresql-contrib cmake libmagic-dev
  29. ```
  30. ### Install Elixir and Erlang
  31. * Download and add the Erlang repository:
  32. ```shell
  33. wget -P /tmp/ https://packages.erlang-solutions.com/erlang-solutions_2.0_all.deb
  34. sudo dpkg -i /tmp/erlang-solutions_2.0_all.deb
  35. ```
  36. * Install Elixir and Erlang:
  37. ```shell
  38. sudo apt update
  39. sudo apt install elixir erlang-dev erlang-nox
  40. ```
  41. ### Optional packages: [`docs/installation/optional/media_graphics_packages.md`](../installation/optional/media_graphics_packages.md)
  42. ```shell
  43. sudo apt install imagemagick ffmpeg libimage-exiftool-perl
  44. ```
  45. ### Install PleromaBE
  46. * Add a new system user for the Pleroma service:
  47. ```shell
  48. sudo useradd -r -s /bin/false -m -d /var/lib/pleroma -U pleroma
  49. ```
  50. **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.
  51. * Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
  52. ```shell
  53. sudo mkdir -p /opt/pleroma
  54. sudo chown -R pleroma:pleroma /opt/pleroma
  55. sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma
  56. ```
  57. * Change to the new directory:
  58. ```shell
  59. cd /opt/pleroma
  60. ```
  61. * Install the dependencies for Pleroma and answer with `yes` if it asks you to install `Hex`:
  62. ```shell
  63. sudo -Hu pleroma mix deps.get
  64. ```
  65. * Generate the configuration: `sudo -Hu pleroma MIX_ENV=prod mix pleroma.instance gen`
  66. * Answer with `yes` if it asks you to install `rebar3`.
  67. * This may take some time, because parts of pleroma get compiled first.
  68. * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.
  69. * 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):
  70. ```shell
  71. sudo -Hu pleroma mv config/{generated_config.exs,prod.secret.exs}
  72. ```
  73. * The previous command creates also the file `config/setup_db.psql`, with which you can create the database:
  74. ```shell
  75. sudo -Hu postgres psql -f config/setup_db.psql
  76. ```
  77. * Now run the database migration:
  78. ```shell
  79. sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
  80. ```
  81. * Now you can start Pleroma already
  82. ```shell
  83. sudo -Hu pleroma MIX_ENV=prod mix phx.server
  84. ```
  85. ### Finalize installation
  86. 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.
  87. #### Nginx
  88. * Install nginx, if not already done:
  89. ```shell
  90. sudo apt install nginx
  91. ```
  92. * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
  93. ```shell
  94. sudo apt install certbot
  95. ```
  96. and then set it up:
  97. ```shell
  98. sudo mkdir -p /var/lib/letsencrypt/
  99. sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
  100. ```
  101. 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).
  102. ---
  103. * Copy the example nginx configuration and activate it:
  104. ```shell
  105. sudo cp /opt/pleroma/installation/pleroma.nginx /etc/nginx/sites-available/pleroma.nginx
  106. sudo ln -s /etc/nginx/sites-available/pleroma.nginx /etc/nginx/sites-enabled/pleroma.nginx
  107. ```
  108. * Before starting nginx edit the configuration and change it to your needs (e.g. change servername, change cert paths)
  109. * Enable and start nginx:
  110. ```shell
  111. sudo systemctl enable --now nginx.service
  112. ```
  113. If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
  114. ```shell
  115. sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
  116. ```
  117. #### Other webserver/proxies
  118. You can find example configurations for them in `/opt/pleroma/installation/`.
  119. #### Systemd service
  120. * Copy example service file
  121. ```shell
  122. sudo cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
  123. ```
  124. * Edit the service file and make sure that all paths fit your installation
  125. * Enable and start `pleroma.service`:
  126. ```shell
  127. sudo systemctl enable --now pleroma.service
  128. ```
  129. #### Create your first user
  130. If your instance is up and running, you can create your first user with administrative rights with the following task:
  131. ```shell
  132. sudo -Hu pleroma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
  133. ```
  134. #### Further reading
  135. {! backend/installation/further_reading.include !}
  136. ## Questions
  137. Questions about the installation or didn’t it work as it should be, ask in [#pleroma:libera.chat](https://matrix.to/#/#pleroma:libera.chat) via Matrix or **#pleroma** on **libera.chat** via IRC.