limepotato/akkoma
1
0
Fork 0
Code Pull requests Activity

Add a note on what OTP releases are

Browse source
This commit is contained in:
rinpatch 2019-06-27 09:45:13 +03:00
parent f5f1bb35c3
commit 4f44732100
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/installation/migrating_from_source_otp_en.md
View file

@ -1,4 +1,6 @@
# Switching a from-source install to OTP releases # Switching a from-source install to OTP releases
## What are OTP releases?
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.
## Why would one want to switch? ## Why would one want to switch?
Benefits of OTP releases over from-source installs include: Benefits of OTP releases over from-source installs include:
* **Less space used.** OTP releases come without source code, build tools, have docs and debug symbols stripped from the compiled bytecode and do not cointain tests, docs, revision history. * **Less space used.** OTP releases come without source code, build tools, have docs and debug symbols stripped from the compiled bytecode and do not cointain tests, docs, revision history.