Added a little note about the config cache command

[PaoloFalomo]

... that would have saved me 2 hours of useless search eheh...

[GrahamCampbell]

I think the real problem is that people don't understand the consequences of running this command originally. I think we need to improve documentation for the command itself too.

[PaoloFalomo]

@GrahamCampbell yep! For example on Why this solved my issue. I'm reading the docs right now about that command that i already know but didn't get that was related to this.

we might reference that command to https://laravel.com/docs/5.4/configuration#configuration-caching

[GrahamCampbell]

Yeh. Often debugging software can be obscure. :)

[PaoloFalomo]

now back to my artisan work! 💻 Hope that @JeffreyWay or @taylorotwell accepts this tiny contribute.

I am pretty new to Laravel (6 months) and loved it since first moment. ❤️ I'd really like to go to the Laracon this year 😃

[taylorotwell]

I don't know. I agree this feels like a random and hacky note to add that needs more context.

[ruchernchong]

I do have this problem sometimes. When a configuration is changed, the settings are being cached and that command php artisan config:cache will solve such problems.