A Rebar3 plugin providing providers to interact with Hex.pm for publishing and managing Erlang/Elixir packages.
rebar3_hex is a plugin for the Rebar3 build tool that provides a set of commands (providers) for interacting with the Hex.pm package repository. It allows Erlang and Elixir developers to publish, manage, and authenticate packages on Hex.pm directly from their Rebar3 environment, streamlining the package publication workflow.
Erlang and Elixir developers who are package authors and need to publish or manage their libraries on the Hex.pm repository.
Developers choose rebar3_hex because it integrates package management directly into the Rebar3 toolchain, offering a secure, feature-rich, and official way to handle Hex.pm operations without leaving their build environment.
Rebar3 Hex library
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates directly into Rebar3 with unified commands like `rebar3 hex publish` and `rebar3 hex cut`, streamlining Hex.pm operations without leaving the build tool, as shown in the basic usage examples.
Offers a full suite of providers for authentication, publishing, owner management, retiring packages, and searching, covering all essential Hex.pm interactions detailed in the README's provider overview.
Supports encrypted user tokens and organization key generation for CI, with clear steps for auth and key management in the authentication and organization sections.
Includes a `build` provider to preview package tarballs without publishing, reducing errors by allowing authors to inspect outputs first, as mentioned in the build provider description.
Requires configuration of external documentation providers like rebar3_ex_doc or edoc, adding complexity and potential compatibility issues, as noted in the setup section where users must choose and configure a doc provider.
Involves managing passwords for token encryption and decryption, which can be cumbersome and error-prone, especially in automated environments, as highlighted in the user auth steps.
The README warns against incorrect plugin placement in rebar.config to avoid becoming a dependency for users, requiring careful setup that could lead to issues if misconfigured.