0
Hello!
After a project is done in Laravel, which folders and files are really useful for uploading to the server?
Actually I use everything and I think it’s kind of heavy.
1 answer
1
As soon as your project using Laravel is published in production, some settings are recommended to optimize it.
1.In the archive .env switch to the new Nvironment.
APP_ENV=production
2.Optimization of Autoloader.
composer install --optimize-autoloader
3.This setting converts all Laravel settings files into a single cache file, reducing the number of paths the framework will need to perform, resulting in a shorter run time.
php artisan config:cache
4.If your project has a large number of routes, it is recommended to use the command below to reduce your routes in a single function next to the cache files, improving site performance.
php artisan route:cache
Further information in the documentation: https://laravel.com/docs/5.5/deployment#Optimization
-
can do this before uploading to production server?
-
Gave the following problem
Logiexception : Unable to prepare route [api/user] for serialization. Uses closureSecond that link is because I probably have routes within group
Browser other questions tagged laravel deploy
You are not signed in. Login or sign up in order to post.
All folders of the project... !!!
– novic
Holy cow! rsrs
– adventistaam
It’s not like java web that we just create a . War and it was already rsrs
– adventistaam
It exists when the server communicates with Git-like repositories but in your case I figured out to summarize it’s all the same
– novic
Thank you very much.!
– adventistaam