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

How to deal with private package #42

Open
gravataLonga opened this issue Oct 14, 2021 · 2 comments
Open

How to deal with private package #42

gravataLonga opened this issue Oct 14, 2021 · 2 comments

Comments

@gravataLonga
Copy link

Hello, with old way you can add private repository into $HOME/.composer/config.json into repositories key json.

But with this new way you need first make it fail at first (because It create folder for project) then update composer.json in there.

Any other solution or I missing something?

@greg-1-anderson
Copy link
Member

Private repositories are not supported. It would be possible to add a feature to set this up. The simplest way might be to just have cgr copy all of the private repos from the default global config into each new composer.json that it created. There are probably other strategies that would work as well. PRs welcome.

@gravataLonga
Copy link
Author

@greg-1-anderson yeah, I agree. Let me try to make this PR

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

2 participants