Laravel is installed into the vendor/ folder with all of your other composer packages (if any).
I don't commit the vendor folder into source, some people do to ease deployments however. What I do is commit the composer.phar inside of the project directory. You also should commit the composer.lock file (and remove it from the gitignore, I'm not sure why its ignored to be honest).
On deployment you can run composer install --no-dev and your migrations. You might write a bash script or something similiar to deal with that.
A more advanced way to manage deployments would be to use something like Capistrano, Rocketeer or Laravel's Remote component.
Wow, excellent advice. Thanks very much for the assistance. I'll do the steps you describe to start with, and then I'll look into Laravel's Remote component.
Thanks again!
Just as a side note - Bitbucket doesn't really "recognise" Laravel, it's a hosted version of Git - and Laravel comes with a .gitignore file that Bitbucket is reading when you commit to the repository - that's why it's automatically ignoring certain files and folders (such as the "vendor" directory).
Running composer install in production would be a good solution if your production host has composer installed. What is the recommended solution for deployments if you are on shared hosting?
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast