Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong config instructions #199

Open
wojtekmach opened this issue Feb 12, 2021 · 5 comments
Open

Wrong config instructions #199

wojtekmach opened this issue Feb 12, 2021 · 5 comments

Comments

@wojtekmach
Copy link
Contributor

I tried following

http://rebar3.org/docs/package_management/hex_package_management/#config

but it doesn't work:

$ rebar3 hex api_url
===> Command api_url not found in namespace hex

$ rebar3 hex api_url http://localhost:4000
===> Command api_url not found in namespace hex

I'm on:

$ rebar3 version
rebar 3.14.2+build.4911.ref56039119 on Erlang/OTP 24 Erts 11.1.7

$ rebar3 plugins list
--- Global plugins ---
rebar3_hex (6.10.3)
@wojtekmach
Copy link
Contributor Author

I was able to set the desired configuration by editing the config file:

%% ~/.config/rebar3/rebar.config
{plugins, [{rebar3_hex, {git, "git://github.com/tsloughter/rebar3_hex.git"}}]}.
{hex, [
  {repos, [
    #{
      name => <<"test_repo">>,
      api_key => <<"secret">>,
      api_url => <<"http://localhost:4000">>}]}]}.

@paulo-ferraz-oliveira
Copy link
Collaborator

At the same time (@tsloughter, if you prefer I can open different issues), with rebar 3.14.3 on Erlang/OTP 21 Erts 10.3.5.15 + rebar3_hex 6.10.3:

rebar3 hex key -a
===> Uncaught error in rebar_core. Run with DIAGNOSTIC=1 to see stacktrace or consult rebar3.crashdump

@starbelly
Copy link
Member

@wojtekmach Yeah, I think I'm going to do a PR to rebar3.org docs and to pull out all that documentation around commands that have yet to be implemented. It's quite confusing. Better to have no docs with a plan to get implemented vs docs out there that suggest "this should work" IMO.

@starbelly
Copy link
Member

@paulo-ferraz-oliveira Yes, please open a separate issue so we can keep scope small. It should not crash.

@paulo-ferraz-oliveira
Copy link
Collaborator

Will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants