I have a basic question about using config.exs in a mixed Erlang/Elixir environment.
I am running an existing Erlang node that includes my Elixir dependencies, by literally adding them to the -pa switch:
-pa ../game_database/_build/dev/lib/*/ebin -pa ../game_database/_build/dev/consolidated
This way I can directly include Elixir applications
in an existing Erlang codebase (I use application:ensure_all_started
to recursively include the applcations β including this Elixir one).
which seems to work until I start relying on variables created and maintained in config/config.exs. Iβm running the build and trying to see where these variables might end up in the /ebin and canβt seem to make any headway.
These config variables are definitely not being included, as I can see a stacktrace when I try to start the application with them.
In Erlang-world the configs are stored in various *.config files that can be referenced from sys.config, but I donβt seem to see any of this as the result of a mix build.
Is it true to say that all my /lib .exs files might end up in the /ebin of the app directory of __build but that /config .exs files donβt? If this is the case, how do I make sure they are βcompiledβ to Erlang-compliant .config files?
thanks,
daniel