Rebar3 shell tries to run applications from relx block?

Questions / Help
1

I’ve got some extras that I want packaged with my release – observer_cli, recon, etc. – so I put them in the relx section of my rebar.config.

I don’t put them in deps; I put them in profiles.prod.deps. I do this because I don’t want one of them included or running during development (because it relies on things that only exist in our production cluster).

Now, when I run rebar3 shell (or rebar3 auto), rebar attempts to start those applications, which results in scary-looking warnings.

What’s the expected behaviour here? How do I include things in my release, but not during development?

2

you could put the relx section in the prod profile as well.

‘rebar3 shell’ starting relx apps is documented behaviour, see ‘rebar3 help shell’