Drupal Installation Profiles (in Drupal 7) are pretty powerful and can do just about anything a module can do. I'm using an Installation Profile along with Features to develop my site, keeping everything in code so I don't have to version my database.

Given the power of Installation Profiles, many of the things you can do in a Features module can also be done in an Installation Profile. E.g., creating content types, configuring permissions, etc. How should you go about deciding whether something belongs in an Installation Profile or in a Features module when using a Code Driven Development workflow in Drupal?


I've recently started using the Features module as a deployment system, as described in this presentation on features deployment. Assuming your using a similar setup with hook_update_N, features has one clear advantage that I'm aware of: it's aware of any changes that are not in code. This makes it a fair bit easier to track changes to (for example) views and content types, and also allows you to auto-generate the new features code to be committed and deployed.

I'm not overly familiar with installation profiles, but from the link you've provided it doesn't look like they provide this functionality. However it might be a case of use whichever suits you the best.

Edit: rethought response.

| improve this answer | |
  • 1
    Profiles can have update hooks, they're pretty much modules in Drupal 7 – Chaulky Feb 16 '12 at 19:40
  • One of the issues I've run into is that not everything can go in a feature, and even when it can, it doesn't always play nicely when enabling all the features at once. For example, I've had issues putting different taxonomy vocabularies and permissions in different modules. In that case, a SQL exception prevented the modules from enabling correctly. – Chaulky Mar 17 '12 at 4:54

I'm using drush quite a bit for this. I have three combined commands (never tried it in one line lol) that I execute after installing Drupal. I got most of the things up and running quite quickly.

So many things you can do with Drush. Downloading and enabling multiple modules is as simple as

drush dl rules views admin_menu && drush en -y rules views admin_menu && drush dis -y toolbar

multiple views can be imported per module easily https://www.drupal.org/node/1393228.

Just annoying that I can't import multiple rules (without the Features module).

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.