Posts tagged deployment

Introduction

Most Laravel deployment procedures assume one of two extremes:

• full root access on a dedicated server (and run composer install directly on the box)
• cPanel-style shared host where you shuffle a public/ folder into public_html and call it directly.

Neither model fits a workspace that hosts multiple in-flight branches of the same Laravel 11/12 application and needs to switch the live code version without restarting Apache or moving gigabytes...

Often during the development of a Laravel application, there are cases where it is necessary to implement the debugged code on a live server. It takes a long time to transfer all the code (including packages and modules) even at a high transfer rate. The solution is to update only the latest, changed code files.

In the case when the (vendor) packages are unchanged, and we need to update the files of our own application, we can use the incremental file transfer using the git versioning...

It is recommended to do an initial installation on hosted server without all dev packages and tools. The best approach is to prepare a local docker installation where it is possible to run composer and NPM. For this purpose, we can use an intermediate server for clean code generation in PHP and css/js. The server is also used for final testing of the application before a transfer of cleaned code to the live server.

In order to have the closest possible conditions for running the...