 
   TODO: Implement custom vm.args.
 
-  ## Internals
-
-  This section covers some details about how releases are assembled.
-
-  ### Structure of a release
-
-  A release is orgnized as follows:
+  You may also set `ELIXIR_ERL_OPTIONS` inside `bin/start` to dynamically
+  set VM options.
+
+  ## Directory structure and environment variables
+
+  A release is organized as follows:
 
       bin/
         RELEASE_NAME

        COOKIE
        start_erl.data

  ### Environment variables

  The system running under releases has the following environment variables set:

    * `RELEASE_ROOT` - points to the root of the release. In the system
      includes ERTS, then it is the same as `:code.root_dir/0`

    * `RELEASE_NAME` - the name of the release. It can be overridden when
      the release is started

    * `RELEASE_VSN` - the version of the release. It can be overridden when
      the release is started

    * `RELEASE_COOKIE` - the release cookie. It can be overridden when the
      release is started

    * `RELEASE_NODE` - the release node name. It can be overridden when the
      release is started

  ### Hot Code Upgrades

  Erlang and Elixir are sometimes known for the capability of upgrading
  a node that is running in production without shutting down that node.


  embed_template(:start, ~S"""
  #!/bin/sh
  # Feel free to edit this file in anyway you want
  set -e

  # Sets and enables heart (recommended only in daemon mode)
  # HEART_COMMAND="$(dirname "$0")/start"
  # export HEART_COMMAND
  # export ELIXIR_ERL_OPTIONS="-heart"

  # To start your system using IEx: "$(dirname "$0")/<%= @name %>" start iex
  # To start it as a daemon using IEx: "$(dirname "$0")/<%= @name %>" daemon iex
  "$(dirname "$0")/<%= @name %>" start
