We happily announce our Multi User - Invitations feature! Our users needed an option to add more team members with tailored access rights for a specific project.
So we created the “Invitations” section in our menu bar on the left. By entering this page, you will be able to invite other team members or view the invitation for yourself.
You can assign specific projects to a team member, be it developer, support manager or project manager; as well as you can give your customer read access to the customer’s project without exposing your other projects. This access policy feature provides new possibilities for an open and understandable workflow with Drop Guard.
What modules do I use? How often are they used in my project? In which projects? Which version exists? Is it the same version as on drupal.org? Might a specific module be a threat for my project(s)?
These and many more questions will be answered within one click on our “Modules overview page” on the left in the menu bar. Check out this short post to learn more about our new feature!
Among other reasons, this feature was requested by our users as they also want to track whether a module is quite relevant for a project or less critical within an update process.
We founded an independent update automation company, including the Drop Guard Drupal update service! Learn more about the App Guard GmbH journey so far in this announcement post.
But first, where do we come from?
Drop Guard was built by the German Drupal company Bright Solutions in 2014, after the idea was born to optimize the internal update process as much as possible - no more wasted time on updates, no fear of Drupalgeddon, no annoying update tasks.
The platform service was optimized and adapted continuously besides other projects of the company, until Manuel Pistner, CEO of Bright Solutions, decided to form a team for this project, that already counted important customers.
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.