We attended the CeBit 2018 in Hanover, Germany, for the first time last week!
But this time we presented our newest extension of update automation management: AppGuard
Besides Drop Guard for Drupal update automation, we also want to provide a SaaS for everyone who uses package and dependency managers like npm, Composer, Yarn, Bundler and more. And we couldn’t believe the great feedback!
We will be part of the great Innovation and Digitalization Business Festival “CEBIT” next week in Hanover, Germany.
Max, Joe and I will attend this fair which will welcome over 300.000 attendees, looking forward to great talks and meetups.
You can meet us at our booth C30/6 in Hall 027, where we will talk about update automation for dependency and package manager files. Besides Drop Guard, our Drupal update automation platform, we are presenting our next smart tool for you to automate your update pipelines beyond Drupal based systems.
Update automation sounds nice as long as you don’t think about your (heavily) patched Drupal project, right?
In this “recipe” I will explain how Drop Guard handles custom patches within an fully or partly automated update process.
1. Update release
An update got released on Drupal.org. Only a few minutes later, Drop Guard detects the update release information, such as update type and version.
A lot of Drop Guard users faced their first Highly Critical SA-CORE-2018-002 update within the PSA-2018-001 release last week. We interviewed a bunch of them and want to share Drop Guard’s performance with you. This means that we will share its achievements, its flaws and its “should have performed better”.
The Good - hard data about Drop Guard's victory
Until today, Drop Guard performed 7370 updates for Drupal agencies and their clients all around the globe.
I've collected a bunch of articles for you, where Drupal agencies describe their processes, workflows and experience with the Drupal update release PSA-2018-001.
Hard facts: The update was announced one week earlier and released on March 28th between 18:00 and 19:30 UTC. Due to the flood of site views and very motivated F5 finger exercises, Drupal.org was down for around an hour. Fortunately, the Drupal Community worldwide was prepared with snacks, pizza, and more pizza, remote hangman, and a lot of memes.
For detailed information, the Drupal Security Team provided this FAQ about SA-CORE-2018-002.
This article is meant to be a further step to raise agencies’ and also customers’ awareness of the huge expenses when it comes to update management in Drupal.
It’s not about promoting a single solution or product. It’s about getting more sensitive for processes which could or should be way smarter and more efficient than they are in most companies right now. It’s about creating processes which are ressource friendly, customer focused and support automation.
Speeding up your Drupal site is not that hard. Following some quick steps can ensure optimum speed for your Drupal website. Read this article to find out. A guest post by Hassan Raza from Cloudways Hosting.
Drupal, as we all know is an immensely popular and customizable CMS, in fact many refer to it as a CMF. However, when building a site with a CMS like Drupal, speed of the website is often overlooked. Although Drupal 8 is pretty well-optimized out-of-the-box, some practices tend to slow down the site.
Hello everybody! You might've experienced some changes of the project settings interface already - here’s the broad summary of what makes Drop Guard more efficient and more powerful now: composer package manager mode, speeding up the setup of update type behaviors (with a short mode option) and live site monitoring.
Automatic updates have been discussed since years already. The pro and con of letting Drupal update itself are discussed in different Drupal.org issues queues. It was not a big surprise that Dries mentioned automatic Drupal core updates as part of the strategic roadmap of Drupal in his Driesnote at DrupalCon Vienna 2017.