News for hackers. Stuff that matters.
Re:Introducing Opencall by elwell on Monday March 31, 2014 @10:01PM (#7505694)
> Don't store your vendor directory in Git! Completely unnecessary and waste of 47MB.

I find that it simplifies versioning as well as making it so you don't have to download individual dependencies. What is your suggestion otherwise?

Re:Introducing Opencall by Tomdarkness on Monday March 31, 2014 @10:06PM (#7505711)
There is a composer.json and composer.lock file in the repository. All you'd need to do to download all the dependencies is have composer installed and run "composer install".
Re:Introducing Opencall by MichaelGG on Monday March 31, 2014 @10:45PM (#7505851)
Thus making your application build process require full Internet connectivity, and making it require that every dependency hosting site is working.

Committing dependencies is a solid decision to avoid taking a dependency on a bunch of third parties.

Re:Introducing Opencall by lstamour on Monday March 31, 2014 @11:10PM (#7505939)
"application build process" or simply the checkout process? I'd suggest your deployment process shouldn't include a public git repo others can change. Instead, use your own fork on Github, or alternatively host a git repo local to your deploy network. After all, you're trying to avoid dependencies on things like Github working/failing, right? ;-)
Re:Introducing Opencall by jarofgreen on Tuesday April 01, 2014 @03:19AM (#7506627)
I do this.

I know what you are meant to do is check in your composer.json and composer.lock then do a composer install on the server.

But then you have a external dependency on your install process on live servers, which is a terrible idea. To got around this, I've seen companies say "we have our own package mirror". Or you could just check in the vendor folder?

Another reason I do it: My software package is used by people who aren't PHP programmers and I want them to be able to just grab the files and go with no fuss.

I do appreciate having the vendor folder in git takes space and is a pain ... but I think the trade off is worth it.

Re:Introducing Opencall by meritt on Monday March 31, 2014 @10:04PM (#7505707)
That's what composer is for
Re:Introducing Opencall by markdown on Monday March 31, 2014 @11:10PM (#7505936)
what is composer, and why do I have to learn it if it is completely unnecessary?
Re:Introducing Opencall by ianhawes on Monday March 31, 2014 @11:58PM (#7506099)
Composer is the de facto PHP package manager, and it is highly recommended for modern PHP applications.
Re:Introducing Opencall by sexmonad on Monday March 31, 2014 @11:18PM (#7505969)
What is <insert technology>, and why do I have to learn it if <insert worse technology> is sufficient?
Re:Introducing Opencall by SEJeff on Monday March 31, 2014 @10:26PM (#7505779)
If you must... use submodules.