Errors in production

A common mistake people do when they deploy tier code to production is that they forget to create a new app_key

• make sure you installed composer 's dependencies
• make sure you ran php artisan key:generate
• enable php errors from php.ini or by adding this to your index.php

error_reporting(E_ALL);
ini_set('display_errors', 1);

@AHMEDDABAK - Thankfully I did run key:generate before (I had to check)

composer did run

and I'm dropping in the display_errors stuff now, but quick question: if I change the debug setting in my .env file shouldn't I see errors without having to add that line?

@JKDESIGN1 - It depends on the error type, and when exactly it happen, if the error happens in one of your controllers after the laravel app is bootstrapped, and the exception handler is initialized, then laravel will catch the error and will display it using the whoops package, if the error is the result of a wrong path, or a file permission or any other reason that happens before the app is booted then you will need php errors to see what went wrong.

Ok so this is weird...it's an error in that it's saving garbage data...because its bypassing the Request validation for some reason.

Locally if I just hit the SAVE button on a new page I get a bunch of errors...like MessageBag errors telling me a whole bunch of stuff is required and that's EXACTLY what I want

Production...just skips the Request and attempts the throw the data...which is all null into the DB you get the 500

Why the heck is it skipping the Request validation in Production?

I...can't believe this irony in what I'm going to say, but the issue was a mis-configuration of Rollbar...my error logger. My error logger was erroring and throwing an error that couldn't be recovered from...I'd laugh it I was dead inside from the debug hell I was just in

@JKDESIGN1 - I am happy to know that you fixed the problem :D