Deployments is how Forge gets your website from your source control provider on to your server, ready for the world to access.
Some applications, such as those created with the Laravel framework, may require a
.env file to configure settings such as databases and caches. You can create and edit your Environment file within the Forge dashboard.
Automatic Environment Files
If your project contains a
.env.example file, Forge will automatically copy this and replace some of the settings to match your server's database settings. An empty
.env.example could result in an empty environment file on the first deploy.
# Quick Deploy
Quick deploy allows you to easily deploy your projects when you push to source control. When you push to your master branch, Forge will pull your latest code from source control, install Composer dependencies, and run your migrations.
You can enable Forge's quick deploy by clicking the "Enable Quick Deploy" button within the Apps page of your site within the Forge dashboard.
# Deploy Script
Almost all of the deployment process is set by the Deploy Script found in the Forge UI. By default, Forge:
- Changes into the site directory
- Runs a
- Install Composer dependencies (depending on the site type)
php artisan migrateif there is an
You may configure this script to change or add steps to your deployments.
Zero Downtime Deployments
Deployments may temporarily make your site unavailable. If you need zero downtime deployments, check out Envoyer.
# PHP Versions
If you have installed multiple versions of PHP your deploy script may need to be updated to use the correct version of PHP.
php will always point to the active version of PHP used on the CLI. If you need to use a different version of PHP to that of the default, you must use
7.x reflects on the version used. For PHP 5.6, you should use
# Environment Variables
Forge will automatically inject the following environment variables into your deployment script at runtime:
| ||The Composer path, running under the sites version of PHP.|
| ||Whether the deploy was triggered with a custom deployment trigger.|
| ||The author of the commit.|
| ||The hash of the commit being deployed.|
| ||The commit message.|
| ||Whether the deploy was triggered by clicking "Deploy Now".|
| ||The PHP-FPM process name that is being used by Forge.|
| ||The |
| ||Whether the deploy was triggered by a source control provider webhook.|
| ||Whether this is a re-deployed commit.|
| ||The ID of the Forge server that is being deployed to.|
| ||The name of the branch that is being deployed.|
| ||The ID of the Forge site that is being deployed to.|
| ||The root of the deployment path, e.g. |
| ||The name of ther user deploying the site.|
You may use these variables as you would any other Bash variable:
if [[ $FORGE_MANUAL_DEPLOY -eq 1 ]]; then echo "This deploy was triggered manually." fi
For example, you may wish to prevent deployments if the commit message contains "wip":
if [[ $FORGE_DEPLOY_MESSAGE =~ "wip" ]]; then echo "WORK IN PROGRESS, DO NOT CONTINUE." exit 1 fi
Forge will prefix any injected variables with
FORGE_. Please do not use this "namespace".
# Deployment Triggers
If you're using a custom Git service, or want a service like Travis CI to run your tests before your application is deployed to Forge, you can use deployment triggers. When you commit fresh code, or when your continuous integration service finishes testing your application, instruct the service to make a
POST request to the URL displayed in the Forge dashboard. Making a request to the provided URL will trigger your Forge deployment.
Although you can refresh the site token at any time, you will need to update any services which are using this URL.
# Deployment Branch
You may change the branch that is deployed by updating the deployment branch setting. Once you have updated the branch, you will then need to click Deploy Now to manually trigger a fresh deployment of the new branch.
# Git Remote
This will update the Git remote URL on your server; however, the site will not be removed or become unavailable during the process. The updated Git remote must contain the same repository / Git history as the currently installed repository.
You should not use this function to install an entirely different project onto this site. If you would like to install an entirely different project, you should completely uninstall the existing repository using the "Uninstall Repository" feature.