Drupal

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:

Another sales call today, with a prospective start-upper who thought Drupal might lower his costs to get a web startup launched.

We recently had a new client contact us and ask if we could move their sites over to Pantheon so they could do some in-house development work. Of course we can do that for you!

Mike, looking for information about integrating a data collection Software as a Service (SaaS) offering, asked:

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.

Apparently there's some FUD (Fear, Uncertainty and Doubt) being sown by a few Drupal shops who are spreading downright wrong information about Drupal 8, trying to encourage people to upgrade to 7 now.

The short answer: Not Vulnerable.

We've been asked by several customers about whether they or we are affected by the recently discovered Bash ShellShock vulnerability. And to the best of our knowledge, we are completely unaffected.

Joaquin asks:

Sorry, John.

But when it comes to adding Youtube and Vimeo, you still haven't made the case for not going into the HTML.

Here is a test page I created.

A month or so ago, this question came up in a

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].