summaryrefslogtreecommitdiff
path: root/docs/installation/otp_vs_from_source.include
diff options
context:
space:
mode:
authorHaelwenn <contact+git.pleroma.social@hacktivis.me>2021-08-10 06:09:31 +0000
committerHaelwenn <contact+git.pleroma.social@hacktivis.me>2021-08-10 06:09:31 +0000
commit6c0ebc65fd9cbf4567af14d505f2064766cd6aab (patch)
treeecc1b5e5f9e8dd86e8dc44de2de2b2f7728e09da /docs/installation/otp_vs_from_source.include
parentf4af74b0fca14421ae17cb53a54ca91d3b519c26 (diff)
parent438ad0d3f9fa354b4b59825d7dcfc48ee2fd7e0a (diff)
downloadpleroma-6c0ebc65fd9cbf4567af14d505f2064766cd6aab.tar.gz
pleroma-6c0ebc65fd9cbf4567af14d505f2064766cd6aab.zip
Merge branch 'docs_make_otp_recommendation_clearer' into 'develop'
Make the OPT recomendation clearer See merge request pleroma/pleroma!3485
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.