How to configure httpc profiles with rebar3?

Question

How can I set configuration options for httpc's profiles when using rebar3? Here is the only example being via `erl -config inets.config` that looks like this: ``` [{inets, [{services,[{httpc,[{profile, server1}]}, {httpc, [{profile, server2}]}]}] }]. ``` I tried adopting it to my rebar3 project structure. Code Project was created with rebar3, with standard OTP layout: ``` rebar3 new release myapp ``` Here is my `myapp/config/sys.config`: ``` [ { myapp, []}, {inets, [{services, [{httpc, [{profile, myapp}]}]}]} ]. ``` `rebar.config`: ``` {erl_opts, [debug_info]}. {deps, []}. {relx, [{release, { myapp, "0.1.0" }, [myapp, sasl]}, {sys_config, "./config/sys.config"}, {vm_args, "./config/vm.args"}, {dev_mode, true}, {include_erts, false}, {extended_start_script, true}] }. {profiles, [{prod, [{relx, [{dev_mode, false}, {include_erts, true}]}] }] }. ``` Here is my `myapp.app.src` file for completeness: ``` {application, myapp, [{description, "An OTP application"}, {vsn, "0.1.0"}, {registered…

Accepted Answer

rebar3 itself use inets http clients so when It starts your application in shell, inets is already started and configured. One workaround would be stop inets before your application starts, as It's suggested by rebar3 developer (copied below). Another one would be boot your release in console mode:

```
./_build/default/rel/myapp/bin/myapp console
```

Beside that there is another problem with your project. You have not told you want inets being started for you. You should have this line in `myapp.src`:

```
{applications, [kernel, stdlib, inets]}
```

Or you can list inets in `rebar.config` release section, to tell relx this app should be included in release and started on boot.

```
{relx, [{release, { myapp, "0.1.0" }, [inets, myapp, sasl]} ]}
```

Stop Inets from Loading on rebar3 shell startup

Here is the copy of the full answer by Fred Hebert from the rebar3 mailing list:

We do need inets for package fetching and will likely not turn it off automatically for all use cases as this could compromise general usage of the rebar3 agent in case where the user application does not use inets, but still asks to fetch packages in a subsequent run. The workaround I would suggest would be to use a hook script for it. Hook scripts run before we boot user applications and are regular escripts:

```
#!/usr/bin/env escript 
main(_) -> application:stop(inets). 
```

You can then hook the script in with:

```
{shell, [{script_file, "path/to/file"}]} 
```

in rebar3.config, or with

```
rebar3 shell --script_file test/check_env.escript
```

How to configure httpc profiles with rebar3?

Solution

Problem

Related problems