Dev Corner

Here are the slides from my 2015 Drupal Summit talk, Quality Drupal DevOps!

You can also click here to open in a new window, full screen.

Faster, more secure, more maintainable. Three nice benefits we get from our new standard Drupal server architecture.

More and more I keep running into assertions that Git is a version control tool, and that if you use it for deployment, you're doing it wrong.

Why?

At Freelock we find it to be a very effective deployment tool, and I'm not seeing a solution that meets our needs any better.

Two presentations in particular caught my attention recently mentioned this:

Just a quick note of how we resolved an issue related to an upgrade to Date.

One of our clients wanted to regularly update a list of dealers along with the parts carried at that dealer, and show them on a map.

Kicking off some posts about various performance challenges we've fixed.

N Factorial

[Edit: Thomas point out this is not really factorial, because it's addition of each number in the sequence intead of multiplication].

What can you do about this page being so slow? That's a question we've been asked by half a dozen customers in the past 6 months, and as it turns out, we can do quite a lot.

After using the latest Ubuntu Long Term Support release (14.04) on my laptop for the past few weeks, I upgraded my home workstation on Friday. And hit a few upgrade challenges I thought worth jotting down for posterity (and the next poor sucker who can't find an answer on Google).

Why is it that there is no top-notch Drupal shop in Seattle? There are several small shops here, and several large companies with branches here, but no really top-shelf, world-renowned Drupal shop based in this great city.

There's a little controversy in the Drupal world, a fork by Nathan Haug, aka QuickSketch. Last week he tweeted:

1. EMBRACE YOUR INNER PESSIMIST...

This doesn't mean you can't be your usual, happy-go-lucky self! In fact, it's absolutely vital that you approach any project with a healthy 'yes we can' attitude.

If you've used a web ontology before, or any other large-scale data repository, you're likely familiar with one of the chief concerns facing anyone in such a position: how do you get your data into the system? Moreover, how do you get large amounts of data into the system with (relative) ease? And if you've used a content management system before, you've likely faced a similar, albeit inverted problem: how do you get your data out?

If you can accomplish these preliminary items without a good deal of effort, you're finally left with the task of transforming the data from one, and allowing it to be recognizable by the other.

If, instead, you haven't used either of these, you're likely wondering why on Earth you would want to.