Cache and storage directories not created if not exists
Hello, I have a little question about cache and storage directories, why the framework don't create automaticaly the missing directories, for example when I first deploy my app with rsync, the cache directory in the bootstrap folder don't exist, just like the framework directories in storage folder.
At the end of the composer update an exception is throwing with the message that the cache directory is not writable, same with the sessions or the view directory.
I think this can be automated by the framework, what did you think?
All of those directories already exist in a default Laravel project. If you use rsync to push your code, then you need to use better patterns so that the directories used by the framework don't get excluded.
Most developers deploy their code from a source code hosting facility such as GitHub, so they never have this problem.