Updating drupal modules
The aliases file is located in the .drush hidden folder, (normally) found in the Home folder of the user.
When there is no file, you can create one for all the websites, for example: allwebsites.aliases.Mine looks like this (replace 'account' with the name of the account): Of course, with power comes responsibility! The Drupalgeddon exploit showed us that hackers are faster than ever, when an exploit is anounced.
In order to diminish the hassle, I looked for more scalable update methods.
For SEO purposes, it's advisable to redirect a www to a non-www or a non-www to a www path.
Other modules are not in the repository, like the md_slider module (which is a paid module).
Even if you use one of the external monitoring services, which provide you the information on relevant updates only, see all points listed above for all the other consequences.Imagine you are on a journey or ill or imagine it's a public holiday and no one is babysitting over all your client websites!Security threats like these can be avoided by setting up a crontab that runs during the night to run a update of only Drupal core.I manage around 50 Drupal installations on shared hosting accounts.We have shared hosting (versus dedicated hosting) because most installations are rather small. But when a core security update is released, updating takes too long.