Perhaps you can try adding the .iex.exs file as an overlay to get it included in the release. mix release — Mix v1.20.2
jesse
slouchpie
slouchpie
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.
4
Owens
I did this but it appears not to work for using Distillery like in this guide: https://elixircasts.io/deploying-with-gigalixir-%28revised%29
Am I wrong about this or is there another way to do this with Distillery?
0
jesse
Ah yeah, distillery does overlays slightly differently from elixir releases. You’ll probably need to edit your rel/config.exs file. See Overlays - Distillery Documentation
1
Owens
Thanks for this, I’m still not understanding how to use this to set the overlays to use the .iex.exs file in the rel/overlays/ directory.
Also, after we set this up in the config do we need to create another release or just deploy to gigalixir?
0
jesse
Basically, what’s happening is the Distillery packs up a bunch of stuff into a tarball, but it normally doesn’t include the .iex.exs file so when you remote console into production, the .iex.exs file isn’t there. Elixir releases, which is different from Distillery, will just pick up anything in the rel/overlays directory and include it in the tarball, but I don’t think distillery does that. You have to actually modify your rel/config.exs file and tell it which files you want to include with something like this (untested)
set overlays: [
{:copy, ".iex.exs", ".iex.exs"}
]
Once everything is configured correctly, just commit to git and re-deploy. Gigalixir automatically recreates the release for you.
1
Owens
conceivably
For whatever reason this appears to have stopped working for us on Gigalixir. Any ideas why this might be the case?
(Asking this here in case anyone else is experiencing this problem and stumbles across this thread)
0