title: No-downtime Laravel deployment
body: <p>I want to deploy a Laravel app from Gitlab to a server with no downtime. On the server, I serve the app with <code>php artisan serve</code>. Currently, I'm thinking that I would first copy all the files, then stop the old <code>php artisan serve</code> process on the server and start a new one on the server in the directory with the new files. However, this introduces a small downtime. Is there a way to avoid this?</p>