What Drupal needs: A ‘Profiler’ module. We need more ‘dev to prod’ support.
Posted 5 months ago in Drupal
Really just brainstorming here. I think Drupal would truly benefit from a 'Profiler' module of sorts. We discussed this briefly at one of the sessions at Drupalcon. One of the biggest roadblocks for Drupal development is that, by nature, the codebase is heavily reliant on database configuration. This makes 'development to production' processes cumbersome.
What if there were a module that essentially 'recorded' actions taken upon a database in a development environment, and could then (intelligently) be 'loaded' into the production database (well - stage database first, and then production)?
I can see the potential benefits here, if the module were as robust as I'm thinking.
Thoughts?
2 Comments
Here's a spec off the top of my head:
- Have a module installed on the production side that keeps track of the following:
* dev DB host/user/pass
* module name and/or path to module.install file
- scrape that file for table names
- on the prod. side, latch onto the install hook
- if one of your intended modules is installed successfully, hop on the workflow and grab all of the data from the dev DB for the recently created tables
- Bob's your uncle.
Looks like we're not the only ones with the idea:
http://drupal.org/project/autopilot
Post new comment