Devops With Laravel By Martin Joo -

We need a symlink release strategy. Instead of updating the "current" folder, we deploy to a release folder and then symlink.

Treat your infrastructure the way you treat your code: versioned, automated, and boring. Boring is stable. Stable is fast. Martin Joo writes about Laravel architecture and clean code. If you enjoyed this, stop fighting your server and start shipping. DevOps with Laravel by Martin Joo

* * * * * php /path-to-your-project/artisan schedule:run >> /dev/null 2>&1 If you have multiple servers (load balancer), only run the scheduler on one server (usually the primary). Otherwise, your daily report will run 3 times. 5. Assets are not your server's problem Laravel Mix or Vite? Great. Running npm run prod on your production server is slow and requires Node.js installed on your PHP server. We need a symlink release strategy

Build your assets during the build phase of your pipeline (e.g., GitHub Actions), not the deploy phase . Boring is stable