Problème de token Composer / GitHub

1 1 1 1 1 1 1 1 1 1 Rating 0.00 (0 Votes)
Submit to DeliciousSubmit to DiggSubmit to FacebookSubmit to Google PlusSubmit to StumbleuponSubmit to TechnoratiSubmit to TwitterSubmit to LinkedIn

Si vous rencontrez des erreurs de token quand vous exécuter la comme "composer update" ou "composer install", la solution est la suivante :

Créer un jeton d'accès pour une utilisation en ligne de commande sur le site GitHub

Pour les explications allez sur le site de GitHub : https://help.github.com/articles/creating-an-access-token-for-command-line-use/

Lancer la commande composer config

Allez à sur le site de Composer : https://getcomposer.org/doc/articles/troubleshooting.md et suivez la partie ci-dessous :

API rate limit and OAuth tokens

Because of GitHub's rate limits on their API it can happen that Composer prompts for authentication asking your username and password so it can go ahead with its work.

If you would prefer not to provide your GitHub credentials to Composer you can manually create a token using the following procedure:

  1. Create an OAuth token on GitHub. Read more on this.

  2. Add it to the configuration running composer config -g github-oauth.github.com <oauthtoken>

Now Composer should install/update without asking for authentication.

Submit to DeliciousSubmit to DiggSubmit to FacebookSubmit to Google PlusSubmit to StumbleuponSubmit to TechnoratiSubmit to TwitterSubmit to LinkedIn