Answer the question
In order to leave comments, you need to log in
Laravel preparation for pduction, how to cut off everything unnecessary?
Puzzled by this question. Let's say there is a working application on Laravel, and it's time to deploy to a production server (and not to one, but to a lot), but many files and folders will obviously never be used, ~ 60% of the folder (/vendor), etc. .d. Should I be asking this question at all?
I'm a beginner developer and maybe I can't find the right words to google correctly, so I decided to ask here, don't scold too much if the question is stupid.
If such a task is relevant, then is it done manually, or are there some automated solutions that can calculate which vendor sources are not used in the project.
PS For example, there is a CMS developed on Laravel (October CMS) but its folder structure is different from the one that comes by default.
Answer the question
In order to leave comments, you need to log in
Should I be asking this question at all?You shouldn't, especially if you're a beginner. You can get some microscopic profit, but the chance of shooting yourself in the foot increases many times over.
Laravel has thought of everything for you.
Throw in the files, the maximum that they take up is a couple of megabytes of space.
Execute the command php artisan optimize
. It will generate a loader that will cut off everything superfluous, leaving only the classes used in the application.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question