Closed cetver closed 6 years ago
Update the plugin with the last version (1.3.x).
It has the latest version:
cetver@ubuntu:/tmp$ composer global update fxp/composer-asset-plugin
Changed current directory to /home/cetver/.composer
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
I get errors similar to this as well. It seems that this plugin is not honoring the protocol being used by the rest of composer and instead always uses git+ssh which requires a git token.
@vpassapera For information, the plugin uses the VCS Repositories of Composer, and so, it uses the native system of management of the authorizations. The Oauth Token or Git SSH Key are required because the total of the dependencies is so high, that the limit imposed by Github is quickly exceeded.
@francoispluchino I see. Thank you!
I'll add that to build my build process then hehe.
Maybe I lucked out using the cache or something since it only happens on composer update and not on composer install.
For more performance and use use the native git, see the doc Use no-api option of VCS Githhub driver.
Yeah, I had already enabled that. I just didn't realize I would still need the token.
Easy enough since I'm using geerlingguy.composer in my ansible playbooks.
Testing it out now. (I have a CI job to run composer update daily, and it started to fail recently)
I'm gonna open a new ticket for this.
When attempting to install
npm-asset/browserify
, I'm getting errorComposer version 1.4.1 2017-03-10 09:29:45 fxp/composer-asset-plugin versions : * v1.1.4
Package installs via npm