Developing locally

[BastianHofmann]

Thanks for making this quick-start.

How would you go about developing locally with this quick-start, since the vendor is missing. I tried running composer install locally, but I got some weird git (submodule) issues.

The error I get when pushing to pagoda, after installing the vendor locally:

No submodule mapping found in .gitmodules for path 'vendor/classpreloader/classpreloader'

I've also had similar issues with installing new packages. And not being able to install these packages from the terminal feels weird.

I'd really like to deploy with pegoda box, but this workflow seems a little bit odd.

[briankiewel]

The vendor directory should not be added to your git repository and pushed to Pagoda as that is populated automatically by the composer installcommand initiated by the Boxfile. Any additional dependencies you want/need should be installed through your composer.json file. To develop locally you should be able to just do composer install on your machine and start serving the public directory. I'm not at a computer right now but later I'll put together some quick instructions for developing locally.

[BastianHofmann]

BTW shouldn't be php composer.phar update be run (after_build) instead of php composer.phar install. If I'm not mistaken all dependencies are reinstalled after every build.

[briankiewel]

With how pagoda works, whenever your app is redeployed it does not carry over your previous vendor directory. All dependencies are reinstalled whenever your app is pushed to pagoda so install would be more appropriate than update in this case because we're essentially starting with a blank slate on each push. Composer would technically work if you do an update instead of install, but that's not the normal way of starting fresh and I wouldn't want to depend on it working that way forever.

[BastianHofmann]

Got it. Sorry I'm still new to pagoda.

[briankiewel]

I just tested this and all I had to do was run composer install on my local machine and then I was able to host the Quickstart application by pointing my local web server to the public folder. You will likely need to set up your local environment's database configuration, but that is beyond the scope of this Quickstart. In case you're not familiar with it, information on Laravel's environment-specific configurations can be found at http://four.laravel.com/docs/configuration#environment-configuration.

When time permits I will add some instructions to the readme about running this locally (or feel free to put some together and submit a pull request for it).

[adamontherun]

I ran composer install like you suggested, and updated the environment config - but when I navigate to my public folder, I get the error Failed to start the session because headers have already been sent by "/Applications/MAMP/htdocs/l4test/app/config/proxy.php" at line 1.

If I install L4 not using your quickstart, it works fine. Any ideas of what I'm doing wrong? Thanks so much!

[briankiewel]

Thanks, Adam! I was able to confirm this issue; it looks like there's apparently a space at the beginning of that config file. If you remove the blank space immediately before <?php in app/config/proxy.php that should resolve this.

I'll push a fix for this.

[pmcalabrese]

I've the same issue of Adam. I'll try to follow your advice.

Thanks for the quickstart, very usefull!!

[DanjBethel]

Sorry if this question was already resolved but, everytime I use git push pagoda --all , it loads my entire composer files again. It makes developing quite slow imo because it goes through the entire long upload process again for something as simple as me changing something in my style sheet. Is there anyway around this? Can I simple .gitignore composer.phar ?

[BastianHofmann]

That's how pagoda works. Composer has to install all packages on push.

[DanjBethel]

ok thank you. i guess pagoda can't be perfect. just wanted to make sure i wasn't losing time when there might have been an easier way. appreciate the response and great job on the package.

[DanjBethel]

Hey, is there anyway for me to successfully develop locally using MAMP and then push to pagoda box? I get the above error and I don't really understand the way you say to work around the tunnel

[briankiewel]

@DanjBethel I just pushed some files to app/config/local that will override the Pagoda settings that won't work locally. You'll need to set your local hostname on the local environment setting in bootstrap/start.php in order to tell Laravel to use these settings. More info on setting up the local environment can be found here.

[DanjBethel]

Appreciate the response. I am fairly new to pagoda box especially using it with Laravel. Can anyone give me or direct me to a guide on how to connect to he database? I am using a free pagoda account of course. The artisan error I am receiving is

[PDOException]                                                               
SQLSTATE[HY000] [2002] A connection attempt failed because the connected pa  
rty did not properly respond after a period of time, or established connect  
ion failed because connected host has failed to respond.