Acquia vs. raw drupal

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
Miguel-gdo's picture

I´ve been thinking of tossing up an Acquia Drupal (community edition) install but had a couple questions for the group first. Sorry if they sound newb´ish, just never done an Acquia install yet.

What do you folks use- raw drupal from d.o or the acquia install?
Is there a time/reason when it´s better to use one or the other?
Is there a difference in stability or is it just an advanced starting point vs. starting from the ground up.

It seems the major difference is that the Acquia package contains some of the most popular/productive contrib modules.
I´ve been looking here: https://acquia.com/product-matrix
Is there anything else I´m missing?

Personally, I´ve only ever used the latest package from d.o but have been curious about the Acquia version lately. Heck, I´ve even been thinking of installing 7.x on another box so I can contribute some bug reports. ;)

thx in advance fellow Drupalistas & hope you all have a great ´09!
--miguel

Comments

I use it

Chris Charlton's picture

I use it. It's fine. It's Drupal. If you don't agree with the list of modules it ships with then just choose your own. Install it somewhere local first, to see the additional toys it has (Acquia modules). There's no magic core.

Chris Charlton, Author & Drupal Community Leader, Enterprise Level Consultant

I teach you how to build Drupal Themes http://tinyurl.com/theme-drupal and provide add-on software at http://xtnd.us

I agree. no magic. its

mike stewart's picture

I agree. no magic. its essentially the same - only with a larger "core" set of modules. last I heard Acquia uses the same CVS repository as the Drupal project itself.

i'm personally not a fan of a couple of the "call home" modules - but they can be useful for clients. that need a "red line" to call (aka, support from Acquia)

I'd suggest using it as a base for all Drupal 6 installs. you lose nothing... and gain a better long term path for clients

--
mike stewart { twitter: @MediaDoneRight | IRC nick: mike stewart }

Good points, Mike. Nice

patrickfgoddard's picture

Good points, Mike. Nice bundle of modules to start off with, with the benefit of the hooks into Acquia should a client ever desire.

Standard drupal core or Pressflow

pcher1bw's picture

Is the Aquia Drupal built using the regular core, or does it have the optimizations provided by Pressflow?

Paul Chernick
CEO
Chernick Consulting
(310) 569-2517

No, but Acquia Drupal can be cross-graded

christefano's picture

No, but Acquia Drupal can be cross-graded to use Pressflow instead of Drupal core very easily.

Acquia Drupal uses Drupal

BTMash's picture

Acquia Drupal uses Drupal core. For me, one of the niceties of using acquia drupal has been using their svn repository has an externals in our projects. So anytime Drupal is updated, my various sites get updated to the latest changes in drupal core without me having to hassle with any of the svn files removed when using drush (or worse, download new version of drupal, and drag and drop all the files into the corresponding directory). So even if you don't use the support line from acquia, using their repo has been very helpful.

And you can override any of the extra modules acquia provides with your own 'from the project page' variant (so if you want to use the 3.x branch of cck which has the multigroup stuff, you can do that!).