We are adding a way to deploy updates on a production October CMS installation without the necessity to run Composer and access the server via SSH, such as shared hosting environments. This will be implemented in the free RainLab.Deploy plugin. This is how it will look like:
In a development environment, you can select components that you want to deploy, e.g. the platform core, plugins, themes, configuration, etc.
The system creates a ZIP file and sends it to your production environment via a secure channel.
The production environment extracts and installs the components.
Please review this feature and let us know how important it is to you - https://portal.octobercms.com/c/26-one-click-deployment
daftspunk said: Please review this feature and let us know how important it is to you - https://portal.octobercms.com/c/26-one-click-deployment
This is going to be fantastic!
Hey daftspunk! Thank you very much for that plugin. I watched the HOWTO video and it looks promissing.
There is a question remaining: How would you proceed with a running october V1 on a shared hosting? With filled database and files.
I would do it like that, but I don't know if that's right:
- Put page to maintenance mode (since we have a job application plugin on there and maybe people want to register for a job while doing the update)
- Download the whole thing incl. files and database to our dev server
- Update october to version 2
- Install the new rainlab-deploy tool
- Deploy it to a new subdomain for the moment (we can switch later to the real domain)
But then, how do I deploy all the storage and DB information again?
The deploy plugin supports upgrading v1 sites. It will attempt to convert the configuration to an .env file and then deploy the v2 files to upgrade the site. We recommend doing a complete backup before proceeding with this in case something breaks.
I hope this helps! If you have any other questions, feel free to send us an email.
1-5 of 5