Closed allan-simon closed 9 years ago
Uh this probably got solved already by the new include-file that calls symfony install
rather than composer create-project ....
ok let's close that then.
ok let's close that then.
no actually it needs to be done, because symfony install , is only launched once , and when you have a colleague who clone/vagrant up your project, symfony install will not run, so that he needs composer install
or anytime the composer.lock is udpated
Good point! And I suspect that you have noticed how symfony installer does NOT leave a composer executable anywhere after it finishes installation (sucks when "manually" demoing how to manually download the symfony installer "in order to avoid having to go via composer"...only realize that you cannot even fix the broken-by-install composer.lock file without, yes, go download the composer installer).
for which you have open an issue on symfony/symfony ? :) (honest question, if you didn't , I will)
if you want, you do :)
I'm closing this ticket for now
no problem, i did here https://github.com/symfony/symfony-installer/issues/171 if you want to follow it.
so that when someone vagrant up the machine, it is already development ready.