After a month of Drop Guard's closed beta we aggregated the most important business benefits from our beta testers. We want to share those benefits with you:
Many times during our beta phase I was asked the question if Drop Guard is a hosting platform and will replace the use of Acquia Cloud, Pantheon or Platform.sh (or any other hosting Drupal platform.) The answer is clearly: NO!
On the contrary those Drupal hosting platforms make your life even easier when using Drop Guard to update your Drupal core and contrib modules automatically. In this blog post I want to outline the benefits of each platform and how using these platforms to leverage your work with Drop Guard. To understand the points of integration, let me explain how Drop Guard works in a nutshell.
Yesterday we hosted our first Drop Guard webinar. For those who couldn’t attend, I share the video with you below. Both the participants’ interaction and the number of attendees far exceeded our expectations: more than 70 people watched the free webinar and learned how to update Drupal automatically with integration into development and deployment workflows. First of all, I want to thank everybody who has supported us from the initial idea through to the first closed beta phase and helped us to improve the service. Without the help of the awesome Drupal community we would never reach our ambitious goals to build this product!
Get ready to rumble! Watch how Drop Guard won against Drupalgeddon on 15.10.2014 at 6:00 PM in this live webinar! We're going to run a live demo re-enacting the whole epic match, and you'll learn about the techniques and strategies that Drop Guard uses to sucker-punch any future Drupal security threats. Don't expect a second round: it'll be a technical KO within minutes!
This free, 45-minute webinar takes place via Google Hangout on 27.07.2015 at 4 PM GMT+2. You'll learn the following:
Automated Drupal core and contrib updates have been discussed in the Drupal community on Drupla.org as well as on external blogs since Drupalgeddon in October 2014. The result? Automated updates are a good idea and would prevent Drupal sites from being hacked, but they also bring some inherent problems, such as:
While developing a system to automate Drupal updates and using that technology to fulfill our Drupal support contracts, we ran into many issues and questions about the workflows that integrate the update process into our overall development and deployment cycles. In this blog post, I’ll outline the best practices for handling different update types with different deployment processes – as well as the results thereof.