No content or errors after installing Gulp

I've been following along with the L5 Fundamentals tutorials developing on my Digital Ocean Ubuntu droplet. I'm at the Managing Your Assets tutorial and after installing some various packages including NPM install, Node, and Gulp. I ran a Composer update as I was having trouble getting some of the packages installed and a Stack Overflow thread suggested that may help, I feel like this is where the issues are stemming from.

I managed to get Gulp working and wanted to see my CSS file loading in the browser. I goto my dev url and I'm getting a services.json error, I check the storage folder and it's gone. I thought this was very odd but I uploaded my local copy and set the permissions again. Checked to see if content was visible and now I'm not getting anything, no errors or indication of what could be wrong, furthermore I dont receive any 404s for random URLs. Error logs are not showing anything wrong past the services.json file error.

Obviously this has to be some sort user error on my part so I feel pretty dumb but without an error log I have no idea how to troubleshoot this. I would hate to have to start the L5 Fundamentals tutorial again after following along for 19 videos.

Any help from the laracasts community would be much appreciated.

EDIT: I've fixed this by running the following command "php artisan cache:clear" and then setting permissions to my storage folder again. I'd love to know what I did wrong to avoid any future Laravel development issues.

EDIT 2: After adding a new Composer require I'm receiving the same services.json error until I run "php artisan cache:clear"

jasonherndon

11 years ago

Level 3

Are all of your composer dependencies and the settings in your config/app.php file correct? Are all of the packages you're pulling in L5 friendly? Sometimes when the class loader is running it's files it can error our during compile, so you'd see Composer actually fail. But sometimes, if everything is formatted correctly, but still causes PHP errors, Composer doesn't fail, but the site crashes. As you're saying that running composer causes the crash and that the app cache clearing helps, this is where I'd start to look.

karatechops

11 years ago

Level 1

I did not have my domain URL set in the config file so that may be an issue. The only other dependency other than stuff we pull in during the L5 Fundamentals (HTML Form facade and Flash facade) tutorials is a migrations generator - perhaps that's the issue.

Please or to participate in this conversation.