Use https version to avoid ssh problem when cloning packages #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When run
composer create-project goalgorilla/social_template:dev-master DIRECTORY --no-interaction
I get on 2 packages cloned from github this error:
Error: Permission denied (publickey)
I saw that in genral this package use the https version of the package to install them.
Also select2 and morris should use the https version to avoid this kind of problems.
An approach to solve this in general would be configuring the local environement with:
composer config --global github-protocols https
And after that, a "composer install" will generate a composer.lock with https in all the packages.
Would be good commit in this repo this generated composer.lock in order to avoid the error i get.
If this solution is not ok for who want to install this package and still get error there is a wrokaround that split in several commands the
composer create-project