> My biggest concern about exposing those is that Mix.install/2's are cached
> and, if we expose the directory, people can write to it and then we will
> end-up with state in those.
> On the positive side, all of the files you referenced so far seem to be in
> priv, which means you can do
My biggest concern about exposing those is that Mix.install/2's are cached
and, if we expose the directory, people can write to it and then we will
end-up with state in those.
On the positive side, all of the files you referenced so far seem to be in
priv, which means you can do
Hello,
Currently, Mix.install/2 installs the dependencies specified by the user
under a folder whose name is built based on 3 elements:
- an install root (e.g. ~/Library/Caches/mix/installs), optionally
overridable via MIX_INSTALL_DIR env variable
- the version of elixir and erlang
