Latest

Acquia Search now does more

Some of the most enjoyable Drupal moments for me was the time I spent in 2009  testing Acquia's Search for Drupal. Acquia Search is a plug-and-play service within the Acquia Network, built on Apache Solr and available for any Drupal 6 site.

I think Acquia Search is probably one of the most significant services provided on the Acquia Network and the feature that will continue to attract businesses to not only Acquia but also Drupal.Acquia Logo So although I'm no longer on the Acquia network, I'm pleased to hear that new features have been added to this Apache Solr implementation.

Some of the more significant features being added to Acquia Search include:

  • Attachment Indexing - Utilizing the Apache Solr Attachment module you can now search the text in document files such as PDF and Word documents. This is big! Even cooler, those documents can searched locally or remotely.
  • Multi-site Searches - Search multiple Drupal sites at once.
  • Update to Solr 1.4.1 which fixes a number of bugs.
  • Wildcard Searches

Denial of Service on an Apache server

Last week was a very frustrating time for me. For whatever reason, an unusually number of botnets decided to zero in on my Drupal site and created what I call an unintentional  Denial of Service attack (DOS). The attack was actually from spambots looking looking for script vulnerabilities found mainly in older versions of e107 and WordPress. Since the target of these spambots were non-Drupal pages, my Drupal site responded by delivering an unusually large number of "page not found" and "access denied" error pages. Eventually, these requests from a multitude of IPs were too many for my server to handle and for all intents and purposes the botnet attack caused a distributed denial of service that prevented me and my users from accessing the site.

These type of attacks on Drupal sites and numerous other content management systems are nothing new. However, my search at Drupal.org as well as Google didn't really find a solution that completely addressed my problem. Trying to prevent a DDoS attack isn't easy to begin with and at first the answers alluded me.

I originally looked at Drupal for the solution to my problems. While I've used Mollom for months, Mollom is designed to fight off comment spam while the bots attacking my sight were looking for script vulnerabilities that didn't exist. So with Mollom being the wrong tool to fight off this kind of attack, I decided to take a look at the Drupal contributed model Bad Behavior. Bad Behavior is a set of PHP scripts which prevents spambots from accessing your site by analyzing their actual HTTP requests and comparing them to profiles from known spambots then blocks such access and logs their attempts. I actually installed an "unofficial" version of the Bad Behavior module which packages the Bad Behavior 2.1 scripts and utilizes services from Project Honey Pot.

As I had already suspected, looking for Drupal to solve this botnet attack wasn't the answer. Pretty much all Bad Behavior did for me was to take the time Drupal was spending delivering "page not found" error pages and use it to deliver "access denied" error pages. My Drupal site is likely safer with the Bad Behavior module installed, but it was the wrong tool to help me reduce the botnets from overtaxing Drupal running on my server. Ideally, you would like to prevent the attacks ever reaching your server by taking a look at such things as the firewall, router, and switches. However, since I didn't have access to the hardware, I decided it was time to look at my Apache configuration.

Quoting IT: Andy Grove on Job Creation

"You could say, as many do, that shipping jobs overseas is no big deal because the high-value work—and much of the profits—remain in the U.S. That may well be so. But what kind of a society are we going to have if it consists of highly paid people doing high-value-added work—and masses of unemployed?"

Andy Grove, Intel CEO 1987-2005, Andy Grove: How America Can Create Jobs, BusinessWeek, July 1, 2010

EPiServer releases EPiServer Relate+2

I continue to hear great things about EPiServer from Blend Interactive's Dean Barker and other folks in the CMS industry. Their accolades for this CMS is one of the reasons I decided to begin focusing on EPiServer here at the site.

Honestly, I don't know enough about EPiServer which is why some of the EPiServer fanboys have promised getting together with me sometime to talk about this platform.  Until my education is complete, I'm going to resort to cheap writing by using press releases and blogs to get some of my information out to you about EPiServer. For instance, lets see if this product announcement by EPiServer's marketing gets you interested to hear more about their products:

EPiServer announces the release of EPiServer Relate+2 , a product package for EPiServer CMS 6, which containsEPiServer Community 4 and EPiServer Mail 5. It also includes a sample website which shows how to combine these three products to build a powerful online community. In today’s conversation economy the ability to get involved in websites where users are free to create, organize and share know-how and experiences in the form of words, pictures and videos is becoming more prevalent and Relate+ makes it a seamless experience for community members, community owners and moderators.

Included is support for Open ID where users can use an existing login ID to sign into multiple websites. The same rich text editor found in EPiServer CMS, TinyMCE, is now used for writing blog posts and the MetaWeblog API is also supported, so users can use their favorite blog applications, such as iBlogger for the iPhone or Live Writer for Windows, when creating or editing blog posts. In combination with blog syndication and ping/ pingbacks, Relate+ is a full-fledged blog engine.

Radiant CMS 0.9.0 is out and about

A new version of our favorite Ruby on Rails CMS has been released, Radiant CMS 0.9.0. Obviously, I spoke a little too soon last October when I announced that 0.9.0 was coming soon. Each open source community has their own pace and time-line for releasing the release candidates of their software. In retrospect, I should have noted that Radiant CMS developers like to take their time in making sure the Radiant releases are at a level of quality and stability they're comfortable with before releasing the final versions to the general public.