Download the PHP package mayconbordin/laravel-http-deployer without Composer

Laravel HTTP Deployer

A tool for automated deployment of Laravel applications using HTTP.

This library is for those that have to deploy Laravel applications on shared hosting without SSH access and don't want to use FTP or GIT.

If you want to use FTP and/or GIT check these libraries:

• BrunoDeBarros/git-deploy-php
• lkwdwrd/git-deploy
• banago/PHPloy
• dg/ftp-deployment

Remote Installation

On the server where the application is going to be deployed, you need to drop the deploy.php file at a public accessible directory (e.g. public_html) with 0644 permissions.

You will also need to create a configuration file. By default the file should be called deploy_config.ini and be located in the same directory as the script. Example configuration file:

Where auth_key is a unique key that will be used for authentication. So, your configuration file should have 0640 permissions.

Local Installation

In order to install Laravel HTTP Deployer locally (development environment), just add

to your composer.json. Then run composer install or composer update.

Then in your config/app.php add

in the providers array.

Configuration

You will also need to create a file with the deployment configuration. It's a YAML file that should look something like this:

The deployments section can have multiple entries, each one describing one deployment configuration. The auth_key is a string that will be used to authenticate the deployment with the server, choose it carefully. The version_filename is the name of the version file used to control the deployment version.

In the remote section you specify the host where the deployment is going to occurr by setting the url, whereas the endpoint points to the path where the deploy.php can be accessed externally. The target is the full path to the installation directory on the server. The temp_dir will be used for extracting the package prior to installation and the history_dir is going to store the older deployment versions.

In the local section you only specify the path to the application, the default value is the current directory (.), and the temp_dir for storing the packaged application for deployment.

Files can be excluded from the package by using the ignore list, the patterns are those from the tar command.

The extra_files is a list of key/value pairs, where the key is the current file location and the value is the location of the file in the package. You can use it to include configuration files only meant for deployment, like the .env file. You have to prefix the target location with ./.

The before_scripts can be used to run commands locally before packaging the application for deployment, like tasks for compressing CSS and JS files, removing development libraries, etc.

Obs.: all paths are relative to the current working directory. Preferably the root of your project.

Usage

Deploy

To deploy your application run:

You can also choose which deployment you want to execute:

And if you only want to package the application without deploying it:

Rollback

To rollback to a previous deployment version:

And to rollback (or forward) to a specific version:

You can also choose which deployment you want to rollback:

Status

To see which version is deployed on the remote server as well as all available versions in the history directory:

You can also choose which deployment you want to execute: