I am working with a group that would like to be able to prepackage a drupal-based site that can be distributed to its members. The idea is that the members could download a single package, extract it and load it on their host, and they get not only a functional Drupal site, but a site with specific modules, roles, menus and even basic pages in place. As it stands right now, this packaging would be the core Drupal modules with a modified user module and a couple of other modules. (My hope is that our developer will find a way to remove his mods from the user module so that we can simply extend the core without mucking with it directly, but that hasn't happened yet).
I have a few questions:
1) Would such a packaging violate any licensing, either in letter or in spirit? We are not planning on hiding the Drupality; our goal is just to make it dead simple for folks to get their own sites up quickly.
2) I have been working under the assumption that I would get a copy of the site working the way I want it to appear, and then dump the table contents. Then I would modify this into an install script that could be autorun on startup, similar to the install scripts for modules. Is this a valid and efficient approach to this, or is there a better way?
3) Assuming that #2 is the best way to get the setup propagated, how would I set up the installation so that this file is invoked on startup? Is there a hook in the code that would be the most appropriate spot to insert this?
DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.
