I’ve said it before and I’ll say it again. This forum is sooo good. The advice people give is such high-quality. It’s like living next to the Mage’s Guild.

This is the solution! I just copied my project’s .iex.exs to rel/overlays/.iex.exs and re-deployed and YATA! it worked!

Thanks @jesse

You can do this:

I noticed than when building the release locally and connecting to it, it works:

myapp$ cat .iex.exs
IO.puts "it works"

# terminal 1
myapp$ _build/dev/rel/myapp/bin/myapp start

# terminal 2
myapp$ _build/dev/rel/myapp/bin/myapp remote
it works

However, if I start the release from another directory, it doesn’t work:

# terminal 1
_build/dev/rel/myapp$ bin/myapp start

# terminal 2
myapp$ _build/dev/rel/myapp/bin/myapp remote
(no output)

It seems it’s a matter of where you start your release from and whether that
directory contains the .iex.exs file and so you could change your :releases
Mix configuration to copy the file into appropriate location.

I did notice one thing that while executing code or setting up aliases in the
.iex.exs file work, autocomplete of these aliases does not so it’s seems
it’s not fully supported.

Modifying this part in the created binary you call with bin/myapp remote, so it automatically loads the .iex.exs from wherever it is stored.