Deploying blocks and content to other site environments
If you have a current Drupal site (built in Drupal 8 or later) you no longer need to entirely rebuild your site -- ever again. That doesn't mean it couldn't use a freshening up now and then.
If you have a current Drupal site (built in Drupal 8 or later) you no longer need to entirely rebuild your site -- ever again. That doesn't mean it couldn't use a freshening up now and then.
If you’re making improvements to your sites, even as simple as pushing updates, you’re going to be changing things around. Inevitably, you’ll break something. Wouldn’t you like to find that out before the production site goes down from the “improvements”?
When you build a new website, going live is relatively easy. You get ahold of a domain name, point it at a webhost, put the website code there, and you're up and running!
After a site is live, it gets a lot more complicated.
Go ahead... Make My Changes in Prod
You thought I was going full "Dirty Harry" there, didn't ya? It's okay, I kinda wanted to as well. You can't go wrong with Clint Eastwood.
A client asks about yet another hosting option:
The VPS-2000HA-S includes the following resources:
6GB RAM (burstable)
150GB SSD Disk space
5TB Monthly Bandwidth
4 free dedicated IP's
With as much Javascript work as we're doing these days, I'm starting to do more and more quick one-off utilities in Javascript. Yesterday I had such a task: update over a hundred different ad slot codes that appeared multiple times in a text file.
In our quest to get all things into Matrix, we've also sent Salt events into a Matrix room. This is extremely useful to monitor the results of automatic highstate runs, individual commands, etc.
We just added Matrix notifications to an old Icinga server we have, because why not? We love having everything in Matrix...
DevOps is the union of development, operations, and quality assurance -- but it's really the other way around.
Panacea, or disaster? Drupal 8 Configuration Management was supposed to solve all our woes when it came to dealing with deploying configuration. In many ways it's a vast improvement, but in some ways it has almost made matters worse.
Our branch strategy based on Git Flow did not survive. It was getting a bit old in the tooth, but the final blow was automation.