Skip to content

Possible to force HTTP client Hackney #109

Description

@ebengt

Greetings,
Would it be possible to add a config to force the existence of Hackney, during compilation?

After I switched Erlang version (might not be connected, but after that it started) in the Dockerfile used to build my application, which include tzdata, the database update does not work in the container. Error message:
" missing :hackney dependency..."
Hackney is available in the image, but compiled after tzdata.

As a work around I build, delete tzdata and build again.
But it would be more obvious with a config or env variable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions