Frequently asked questions

Which Laravel versions does the deployment script support?

The deployment script supports Laravel 5 and higher.

Can I use the script for multiple applications?

There is no limit to how many applications you can deploy with the script. After purchasing the script you can use it for as many environments and applications as you want.

Will I receive future updates to the deployment script?

Yes, every purchase includes all future updates.

How can I customize the deployment script?

The deployment script includes "before activation" and "after activation" hooks. You can use these hooks to run any custom commands that your application needs.

You can also add custom steps to the `.gitlab-ci.yml` workflow file. There are many tutorials available online to get your workflow to do pretty much anything.

Do I get a notification if my deployment fails?

By default, GitLab sends out an email when a deployment fails. You can add custom notifications by modifying the `.gitlab-ci.yml` workflow file.

How does this deployment script compare to Laravel Envoyer?

The script deploys your application in almost exactly the same way as Envoyer does. For more details, see this comparison with Laravel Envoyer.

How does deploying to multiple environments work?

By default, the GitLab yaml file has a step that deploys your application when you push a commit to the main branch. If you want to deploy to multiple environments, staging and production for example, you can duplicate that step to deploy to as many environments as you want.

For example, you can configure the workflow to deploy to your staging server when you push a commit to the develop branch, and to deploy to your production server when you push a commit to the main branch. To achieve this, you only have to copy and paste the deployment step in the workflow and then fill in the branch and server details for each step.

What operating systems are supported?

The deployment script is made to deploy your application to a Linux server. It is tested with Ubuntu 16.04, 18.04, 20.04 and 22.04, and with centOS7 and centOS8. The script will not work on a Windows server.

Which PHP version does the deployment script use?

The workflow file that builds your application uses the latest version of PHP by default. This can be easily changed by editing the PHP version number in the workflow file.

The code that runs on your server to deploy the application doesn't use PHP, it is written in bash. This means it doesn't matter what PHP version your server uses.

Does the deployment script automatically run my unit tests?

The script doesn't run tests by default, but you can add this as a separate step in the workflow file.

Can I deploy a non-Laravel application using this script?

Not out of the box, but the deployment script is well-documented and reasonably easy to modify, so changing it to deploy Symfony or Magento for example should be possible.