A simple way to deploy your application to a remote location.
- October CMS 2.1.20 or above
- PHP openssl extension
- PHP eval function
php artisan plugin:install rainlab.deploy
This plugin helps in cases where your remote server (production, staging, etc) cannot use composer or where shell access is limited, an example of this is shared hosting.
The Deploy plugin works by creating a secure channel between your local developer environment and your hosting server. Plugins, themes and core files are then compressed and sent securely to your server and then installed remotely. This approach is similar to an update gateway, except files are pushed to the server instead.
You may use this plugin as a solution to upgrading your website to a newer version of October CMS, for example, if want to upgrade a v1 website to use v2. Always take a complete site backup before performing these steps.
- Install or upgrade to the latest October CMS version locally on your machine
- Deploy the Beacon files to the older site you want to upgrade
- The Deploy plugin will attempt to upgrade the site during its first deployment
If you need support with this process, feel free to send an email to the helpdesk.
Before starting, you should have set up a new site in your hosting manager and ideally have an empty database. You may also apply these instructions to an existing website, including legacy versions of October CMS, however, please make sure you have taken a complete backup in case something goes wrong.
For safety, the deploy plugin will never delete files. It will overwrite and create new files only. If you need to delete something, you should do it directly on the server.
After installing this plugin, navigate to the Settings > Deploy in your October CMS control panel and click Create Server.
- Enter the web address for your site (eg: https://mycpanelwebsite.tld/)
- Generate a new RSA private key, or enter an existing one to set up an existing server
- Download the Beacon ZIP files
In your Beacon ZIP file, you should notice the following files:
- index.php
- bootstrap/app.php
- bootstrap/autoload.php
- bootstrap/beacon.php
You can upload these files anywhere and they will become a target for deployment of October CMS. You can use FTP or the file manager in your hosting control panel.
Important: The directory where the files are uploaded must be writable by your web server (eg: permission 755 for apache).
Once you have the Beacon installed remotely and the server set up locally. It's time to perform your first deployment.
Sometimes you may see an error that a valid response from a beacon was not found.
The first thing to try is the "Check Beacon" link to make sure the beacon is Active, if it says Unreachable, try downloading the beacon files and uploading them again to your server.
You can perform more advanced troubleshooting by capturing the raw response from the server or beacon. To capture the raw response from the beacon, do the following.
- Add
?debug=1to the end of the URL in the backend. - Click Check Beacon or perform the deployment action again.
- Check the log file in storage/logs to see what the server is responding with.
This should hopefully provide some insight in to why the response was not accepted.
There are times when you don't want specific files to be deployed, such as the node_modules directory used in plugins and themes. This is possible by creating a .deployignore file in the base directory of your plugin or theme. This file behaves the same as .gitignore file where you can configure Git to ignore files you don't want to check in.
The following .deployignore file will exclude the node_modules directory:
node_modules/
The file must be located at the base directory of the theme or plugin. For example:
- themes/demo/.deployignore
- plugins/acme/demo/.deployignore
This plugin is an official extension of the October CMS platform and is free to use if you have a platform license. See EULA license for more details.