summaryrefslogtreecommitdiff
path: root/docs/installation/otp_vs_from_source.include
diff options
context:
space:
mode:
authorHaelwenn <contact+git.pleroma.social@hacktivis.me>2021-08-29 18:48:53 +0000
committerHaelwenn <contact+git.pleroma.social@hacktivis.me>2021-08-29 18:48:53 +0000
commit0b2119d4a791b3623b304b0bab683609d23271d4 (patch)
tree40eac155fc0b26d924aa072fd289fc3e64bfad26 /docs/installation/otp_vs_from_source.include
parentdc63aaf84f07a6f8042f43617d8ec356fed85cec (diff)
parent7372609c5b5063d177715d5067654888f7075403 (diff)
Merge branch 'release/2.4.1' into 'stable'v2.4.1
Release: 2.4.1 See merge request pleroma/pleroma!3501
Diffstat (limited to 'docs/installation/otp_vs_from_source.include')
-rw-r--r--docs/installation/otp_vs_from_source.include3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/installation/otp_vs_from_source.include b/docs/installation/otp_vs_from_source.include
new file mode 100644
index 000000000..63e837a53
--- /dev/null
+++ b/docs/installation/otp_vs_from_source.include
@@ -0,0 +1,3 @@
+## OTP releases vs from-source installations
+
+There are two ways to install Pleroma. You can use OTP releases or do a from-source installation. OTP releases are as close as you can get to binary releases with Erlang/Elixir. The release is self-contained, and provides everything needed to boot it, it is easily administered via the provided shell script to open up a remote console, start/stop/restart the release, start in the background, send remote commands, and more. With from source installations you install Pleroma from source, meaning you have to install certain dependencies like Erlang+Elixir and compile Pleroma yourself.