Pagodabox checkout issues
peterver opened this issue · comments
I have been having some issues with the pagodabox quickstart for laravel 4.
An install that i did was using the redis drivers for both session and cache. It is my understanding that by default these are set to native and file respectively ?
Secondly the pagodabox quickstart git clone doesn't pull the dependencies ( even though they are installed as seen when making the live app on pagodabox ).
My solution for the moment was to copy some vendor files from a local install that i did with composer into my pagodabox git folder and setting them up manually :/
Yeah I'll need to adjust the setup a little for local development since I switched to redis. In the meantime, you can create a local config setting to override these configurations. Take a look at the laravel docs for more info on environment specific configs if you're unfamiliar.
Regarding dependencies, git clone will never include composer dependencies. You need to run a composer install in the cloned directory on your local machine to pull the dependencies in. After deployment to pagodabox I have it run a composer install which is why it works there.
just a quick update, to be able to do a composer update and pull in the dependencies with composer ( without having to manually fill in the vendor directory like i suggested earlier ) , all you need to do ( quickfix i know ) is remove the scripts section from composer.json entirely ( http://forums.laravel.io/viewtopic.php?pid=43718 ) I was having issues with composer install :]
Depending on when you initially cloned the repo you may have an out of date composer.json file. A couple of months ago a version with an error in it got into one of the beta releases of Laravel. With the current version of the composer.json file, you should not need to delete anything from composer.json in order to install the dependencies locally.
On the initial local installation (when you don't yet have a vendors directory), you should actually use composer install install instead of composer update. While the composer update will technically do what you want and try to pull in the dependencies, it also causes the pre-update-cmd script from the composer.json to fire off beforehand. That script will fail if the dependencies haven't already been installed via the composer install command. After a successful composer install, then you can keep the local dependencies up to date with composer update.
yup tried composer install on a new app and working perfectly, however did still get some errors with the redis drivers so i changed them back to their defaults ( hope you don't mind ). Migrating from laravel 3 to laravel 4 :] sorry if i'm being a pain in the ass with some ( beginner ) composer issues :]
Closing this issue as I added some local configuration files to the repo that will override the Redis session and cache settings in a local environment. Just need to add your local hostname to the array in bootstrap/start.php to use these configs. This will allow you to use the native and file settings locally, but still take advantage of Redis on Pagoda.