Been thinking about providing my Drupal set-up as a "distribution" -> 2 questions

Events happening in the community are now at Drupal community events on www.drupal.org.
lorlarz2's picture

Been thinking about providing my Drupal set-up as a "distribution" (a complete prefab site that could be shared with other Occupy groups). This has raised 2 questions:

(1) Where-all does Drupal 6 store the site or root address? Is this all stored in
database tables, or does Drupal also write it elsewhere? Where-all in the db tables
(what tables) is the site's address or root address stored? (Of course, this
would have to be changed by everyone who uses the distributions, since their
site root will be different.) Any other changes having to do with the site address
not in the db tables?

(2) Is everything except base files and module files stored as content in database
tables?? Could I: (a) Back-up the whole database of my active (http://99online.us)
site. Then (b), go in as admin (in maintanence mode) in the normal admin interface
and delete all the
content and all but 2 key users. And THEN (c) save a backup of that 'empty'
database to be distributed with the 'distribution' (of all files on my site). And THEN
(d) finally, restore the back-up of my fully-loaded database of my active site AND
expect all to be restored to normal and all to be well???

Comments

More Information

wylbur's picture

There is a right way to create Drupal distributions. Here's documentation on how this is done. It will take some knowledge and work to get it done right, but when you do, you will have something that is really easy for people to install and use.
http://drupal.org/node/642116

Part of the shine of Drupal is that people have worked up processes to create consistent repeatable results. That process takes time, but it gets us good results.

Hope that helps!

A quick look and questions remain

lorlarz2's picture

wylbur,

A quick look at the page you recommended and it seems like that page presupposes that one know the answers to the 2 questions I asked (since they seem to not be addressed).

Perhaps someone would like to help me do it "correctly". But, if I do nothing wrong (and contaminate no files or processes), I would be content just to do it my way. While it may not be totally the standard way. Not wrong, is not wrong.

It's not just you!

wylbur's picture

You are creating a 'distribution' for others to use. If your 'distribution' looks and behaves completely differently from typical Drupal distributions, then the people who will want to use your 'distribution' will face the task of guessing/learning how to use it.

You have to think of the people who will use this. If you follow the rules, it will be easier for them to get working quickly.

You are free to do what you wish, but when we work together creating and using agreed upon standards, we can work much more efficiently.

To your questions:

All configuration is stored in the database tables except - the database and website variables that are in the settings.php file that defines your installation.

Your installation might have some files in the files folder. Instead of uploading file content to the database, this is usually stored in the files folder. The location of that folder is defined in the site information.

Hope that helps.

lorlarz2's picture

P.S. So far, it IS just me ... but thanks for some anwsers.

I am willing to cooperate if I get some help

lorlarz2's picture

wylbur,'
I am willing to cooperate if I get some help. Perhaps, if http://99online.us
is not good enough to inspire help, then perhaps it would go nowhere anyway.
( I do not think the site is bad, in any case, esp. since I have receive absolutely
no help. As far as the Drupal image is concerned, rightly or wrongly, I often feel I do
more for Drupal than the Drupal "community" does for me. If I make Drupal look
good , it is on my sweat alone. -- hey maybe this will stimulate some 'construstive'
criticism' -- I can handle that.)

Twin Cities

Group events

Add to calendar

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: