This forum has moved to a new location and is in read-only mode. Please visit talk.octobercms.com to access the new location.
Hello,
I thought, I will make a short instruction here on how to update october v1 to v2 with deploy plugin, because I experienced some issues, which got solved with the help of the october team. I thought, I could share this here.
You may want to watch the video from october about the deploy plugin here, to get some information on how it should be used: https://www.youtube.com/watch?v=Lx9X3CfXwfw
If you prefer a step by step HOWTO in text, you may follow the steps here on how I was able to preform the major update with deploy plugin:
- Duplicate webpage v1 on shared hosting server with new subdomain, so there's no downtime and I'm able to test before I switch to the new version (I really duplicated all the files on new subdomain and implemented a new database with the same data from the october v1. Don't forget to change the database name and credentials to new generated one on the duplicated page, so each page has it's own files and database.)
- Setup a new October v2 on my local server with database from page v1 (I followed instruction from here: https://docs.octobercms.com/2.x/setup/installation.html. I just took a dump of the database from the server and installed it on my local environment and put the name and credentials of this DB to local v2 page installation when asked.)
- Copy storage, own themes and own plugins to v2 local page from v1 page. (For this step I followed instructions here: https://octobercms.com/support/article/rn-13. Of course I had my v1 page files downloaded on my machine via FTP for this.)
- Install vendor plugins used for the page on local v2 page
- Install deploy plugin on local v2 page
- You may consider doing a backup on the server before proceeding
- Download beacon from local v2 page and deploy it to v1 page on server on subdomain page (if you wonder: you need to overwrite the index.php file and the bootstrap folder with beacon files on server)
- Check that beacon is connected and follow the steps in the deploy plugin interface on local v2 version
- Don't forget to also deploy the config files (I missed this step in first place. The page was working somehow then without this, but I experienced several issues, like uploading files to plugins.)
- What was also an issue then, is that my SMTP didn't work anymore on just updated page. I solved that with deleting the vendor folder on duplicated (now) v2 page on subdomain on shared hosting server and deployed again the core files. (I don't know if this step is needed, as I forgot the config files, like I explained in step 9. Maybe the SMTP works with the config files.)
- Test everything and if it's working, switch the subdomain to the actual domain you used before. (I kept my old v1 page then on another subdomain, to perform a rollback if everything fails.)
Well, this is how I managed it and my page is working now with october version 2. Of course there may be a better way or maybe I forgot something. I'm happy to hear about that here.
1-1 of 1