Activate environment and load all modules that are installed within this module.

Examples

iex> Boyle.activate("boyle_test_env")
:ok
iex> Boyle.deactivate()
:ok

Get name of active environment.

Examples

iex> Boyle.activate("boyle_test_env")
:ok
iex> Boyle.active_env_name()
"boyle_test_env"

Returns a specification to start this module under a supervisor.

See Supervisor.

Activate environment and unload all modules that are installed within this module.

Examples

iex> Boyle.activate("boyle_test_env")
:ok
iex> Boyle.deactivate()
:ok

Get absolute path of active environment.

Show detailed dependencies in the current environment stored in mix.lock file created for the environment.

Examples

iex> Boyle.activate("boyle_test_env")
:ok
iex> Boyle.freeze()
{%{decimal:
  {:hex,
    :decimal,
    "1.7.0",
    "30d6b52c88541f9a66637359ddf85016df9eb266170d53105f02e4a67e00c5aa",
    [:mix],
    [],
    "hexpm"}},
  []}
iex> Boyle.deactivate()
:ok

Invoked when the server is started. start_link/3 or start/3 will block until it returns.

init_arg is the argument term (second argument) passed to start_link/3.

Returning {:ok, state} will cause start_link/3 to return {:ok, pid} and the process to enter its loop.

Returning {:ok, state, timeout} is similar to {:ok, state} except handle_info(:timeout, state) will be called after timeout milliseconds if no messages are received within the timeout.

Returning {:ok, state, :hibernate} is similar to {:ok, state} except the process is hibernated before entering the loop. See c:handle_call/3 for more information on hibernation.

Returning {:ok, state, {:continue, continue}} is similar to {:ok, state} except that immediately after entering the loop the c:handle_continue/2 callback will be invoked with the value continue as first argument.

Returning :ignore will cause start_link/3 to return :ignore and the process will exit normally without entering the loop or calling c:terminate/2. If used when part of a supervision tree the parent supervisor will not fail to start nor immediately try to restart the GenServer. The remainder of the supervision tree will be started and so the GenServer should not be required by other processes. It can be started later with Supervisor.restart_child/2 as the child specification is saved in the parent supervisor. The main use cases for this are:

• The GenServer is disabled by configuration but might be enabled later.
• An error occurred and it will be handled by a different mechanism than the Supervisor. Likely this approach involves calling Supervisor.restart_child/2 after a delay to attempt a restart.

Returning {:stop, reason} will cause start_link/3 to return {:error, reason} and the process to exit with reason reason without entering the loop or calling c:terminate/2.

Callback implementation for GenServer.init/1.

Activate environment and unload all modules that are installed within this module.

Examples

iex> Boyle.activate("boyle_test_env")
:ok
iex> Boyle.install({:decimal, "~> 1.5.0"})
:ok
iex> Boyle.deactivate()
:ok

List all available environemnts created in the past.

Examples

iex> {:ok, envs_list} = Boyle.list() iex> "boyle_test_env" in envs_list true

Create new virtual environment where your modules will be stored and compiled.

Examples

iex> {:ok, envs_list} = Boyle.mk("test_env")
iex> "test_env" in envs_list
true

Print list of modules paths and loaded modules.

Make sure all dependencies are fetched, compiled and loaded.

Remove existing environment.

Examples

iex> {:ok, envs_list} = Boyle.rm("test_env_for_removal")
iex> "test_env_for_removal" in envs_list
false

Get state of Boyle module, some internal paths useful for loaded modules management.