diff options
| author | rinpatch <rinpatch@sdf.org> | 2019-06-27 09:45:13 +0300 |
|---|---|---|
| committer | rinpatch <rinpatch@sdf.org> | 2019-06-27 09:45:13 +0300 |
| commit | 4f44732100a23475a645d9e7070ca0a17934ee49 (patch) | |
| tree | 37a0b2f97b6f303211ddff7e7bc9c82b85a2f490 | |
| parent | f5f1bb35c3736dd591f6689813c7fe95650e4bba (diff) | |
Add a note on what OTP releases are
| -rw-r--r-- | docs/installation/migrating_from_source_otp_en.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/installation/migrating_from_source_otp_en.md b/docs/installation/migrating_from_source_otp_en.md index 46dc7b53b..4d6f20ee0 100644 --- a/docs/installation/migrating_from_source_otp_en.md +++ b/docs/installation/migrating_from_source_otp_en.md @@ -1,4 +1,6 @@ # 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? 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. |