- #DRUPAL 8 UPGRADE CORE SHELL SCRIPT INSTALL#
- #DRUPAL 8 UPGRADE CORE SHELL SCRIPT UPDATE#
- #DRUPAL 8 UPGRADE CORE SHELL SCRIPT FULL#
- #DRUPAL 8 UPGRADE CORE SHELL SCRIPT DOWNLOAD#
My plan, as far as it goes, is to keep loading sites onto it until it shows the first signs of creaking and then upgrade. Jamie, I chose the 2048mb Linode at $80 a month and their backup for $20 a month. However, just using ftp and the Aegir contrrol panel has transformed my working life - What a relief.Īnd no, I'm not on commission! Just thought it might help someone else in my position. I still haven't got around to learning Drush but suspect that when I do it will make things even easier. I've got 50+ sites and counting on the server, all running like lightning and easy to update.Īs Omega8 set it up, they still offer support for the Aegir side of things which helped a lot as I was still working things out. I've now done that and couldn't be happier with the result.
#DRUPAL 8 UPGRADE CORE SHELL SCRIPT INSTALL#
I talked things over with them and they suggested I get a VPS at Linode (allowing me to use Linode's UK servers) and use Omega8's paid installation service to install Aegir. I can't remember the cost per core but it was prohibitively expensive for me. However, I found I could only host about four websites per their standard core (which is how they price things). It was a bit of a learning curve but when I got the hang of it, I loved it. I initially took up Jamiet's suggestion and went to for their hosted Aegir solution. Some months later, I think I've settled on a set up and thought I'd share it with you. Will share details upon request.ĭrush may have a bit of a learning curve initially, but the time it will save you in just a short while is well worth it. Don't even have to put sites in maintenance mode.) Man, my life just got easier! Note: Drush 5 now out has even more valuable commands.Įven if you have 30+ sites under a single instance, this should not be difficult to implement (and the script may take 30 sec- 1 min to run!). (Obviously we do this on devel first, check sites, then move to production. What we do: we have about 30 sites under 4 separate Drupal instances (will soon have 50) and use drush commands in a shell script that cd's to a base Drupal install, does a main pm-update and then visits each site under that install, running updatedb.
Would need to know more details about your specific situation to say any more on your question. Something to consider if you have any command line access-or perhaps hosting service provides an alternative to run scripts. being able to run "drush sql-sync" which does it all in one step will be quite worth it. Managing multisites with drush site aliases is much easier than trying to do it by hand. The key if you want to be able to do it yourself is to have access to be able to use Drush on the server. Acquia and HotDrupal are just two (at different $ and pros/cons). There are hosts that will tune for Drupal and manage the rest of the stack. There are many shared hosting providers that do have SSH access, so a change of hosting might be in order, but it might be something that you want to investigate. It's not the lightest module in terms of processing and efficiency, but it has a lot of benefits like AWS S3 integration. It is a fairly complete module for backing up individual sites. You might look at the Backup and Migrate module.
#DRUPAL 8 UPGRADE CORE SHELL SCRIPT UPDATE#
Each site does well with an individual database and the size of a combined database will be problematic, especially if you want to only update a single site. I would suggest against the one database to rule them all approach. The issues you mentioned are all separate questions that deserve individual responses
#DRUPAL 8 UPGRADE CORE SHELL SCRIPT FULL#
You don't necessarily need to go to a full VPS to get a good multisite setup. If you have no SSH access on a shared hosting, there's very little chance that Aegir will be able to help. I'd really like to get this right now before it all becomes too big and unwieldy to make the necessary changes. Is there a better way that I haven't thought of?Ĭan you pay people to do this updating/admin stuff for you? What if they wrecked your site? Would it be better to use one big database rather than 35+ individual ones? Would it be better to use a VPS with shell access than shared hosting?
So far I'm thinking of putting all the databases together in one big database, downloading it to xampp, updating all local sites using drush and then uploading again to the live site. So I would really like some advice on the best way forward.
#DRUPAL 8 UPGRADE CORE SHELL SCRIPT DOWNLOAD#
I currently have a live Drupal 7 multisite with about 35 sites on it and it will shortly grow a lot bigger.Īt the moment I am using shared hosting without shell access, and when modules/core need updating, I have to download each separate database using phpmyadmin, upload each one to my local xampp copy site, update each site manually and then re-upload each database to the live site.
I'd really appreciate any thoughts on the best way to set up a multisite installation.
0 kommentar(er)
