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

publish using private registry argument #515

Closed
jogelin opened this issue Jan 20, 2017 · 3 comments
Closed

publish using private registry argument #515

jogelin opened this issue Jan 20, 2017 · 3 comments

Comments

@jogelin
Copy link

jogelin commented Jan 20, 2017

I read many discussions about the possibility to publish to a private registry but is there a way to specify a private registry as an argument in the publish command ?

Using npm we can do npm publish --registry http://my-private-registry

I can use the publishConfig configuration in each package.json but it's a duplication which is something that I want to avoid by using lerna ;-)

Do you think it's a good idea to have : lerna publish --registry=http://my-private-registry ?

@rtsao
Copy link
Contributor

rtsao commented Feb 3, 2017

You can do npm_config_registry=https://my.npm.registry.org lerna <command> for all commands.

@hzoo
Copy link
Contributor

hzoo commented Feb 28, 2017

$ lerna publish --registry https://my-private-registry

will be in the next release

@hzoo hzoo closed this as completed Feb 28, 2017
@lock
Copy link

lock bot commented Dec 28, 2018

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants