Love Fuel?    Donate

FuelPHP Forums

Ask your question about FuelPHP in the appropriate forum, or help others by answering their questions.
Should composer.phar and composer.lock be .gitignored?
  • When I clone my repo to a new VirtualHost, I always have to run composer.phar update, which modifies composer.lock. Also, it usually gives me a message to update composer.phar. Should these files be added to .gitignore?
  • HarroHarro
    Accepted Answer
    composer.lock should be ignored, it's generated/updated every time you run composer.

    If you ignore composer.phar, you can't run composer after you cloned the repo, which you have to (if you're on 1.6) otherwise it won't work. So in that case you need to install composer manually on the new server somewhere.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion