rlipscombe
Hex.pm accounts for organisations?
We’ve recently open-sourced some Erlang packages. At the moment, they’re just pushed to GitHub.
I’d like to publish them to hex.pm – if nothing else, to prevent someone squatting on the names.
What’s the best practice for setting up a hex.pm account for an organization? I’m thinking about allowing multiple people to publish new versions of the package, and – worst case – if I leave and have to hand over control of the packages.
Marked As Solved
LostKobrakai
Organizations on hex are a paid feature for private packages. You can however add multiple owners or maintainers to a package without an organization: mix hex.owner — Hex v2.0.6 / rebar3_hex_owner — rebar3_hex v7.0.8
Also Liked
ericmj
Hex organizations are free if you only use them for public packages, only when you need private packages is billing required.
If you have multiple packages organizations makes it easier to manage users and permissions since you can manage them for the whole organization and all its packages instead of each package individually.
Hermanverschooten
I don’t think he means that, he talks about the code being private and that hex helps him with making it available and the versioning is a bonus.
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"