I'm very new to Drupal - but I've started to monkey around in the code... not so much play with it - but start reading it so I understand how it all works.

One thing that I have noticed right off the bat is the conf_init function.

I figure it's purpose is to perhaps allow people to 'hide' their conf.php file by using a name based on the site address. OR - is there a greater purpose for this function?

I hope to be contributing to the project - but first I have to understand it ;-)

andre (with the first of many questions)

p.s. If this is not the place for this kind of question - can you please direct me to the appropriate location. Thanks.

Comments

killes@www.drop.org’s picture

Using differently named conf.php files you can run a whole lot of sites from one Drupal install.

andremolnar’s picture

I hadn't yet imagined using drupal for more than one site at time.

This just goes to show how darn cool drupal is - talk about reducing development time for a series of similar sites.

I've continued monkeying with the code - and I have got to say that I LOVE how drupal is writen.

andre

jsilence’s picture

In the current implementation conf_init tries to guess the different config file names from the URL it was called by. This results in several file_exists calls for EACH PAGE HIT.

I think if you choose to run multiple sites from one installation then it would not be a problem to register the right filename for each site specific config in the central config file.

Just m 2c.

-silence

--
If you can't walk, try to run.

moshe weitzman’s picture

can you do some benchmarks which show that these file_exists calls are costly? i don't think we should give up the flexibility of this feature unless the someone proves that the performance hit is significant.

JonBob’s picture

Good to have you looking at the code, Andre. If you haven't yet, I'd suggest starting in by reading the developer documentation, especially the overviews of the base systems and the example modules. As you're in there, take note of confusing concepts; we would like to improve that reference to make it more useful as a tutorial for new Drupal developers.

andremolnar’s picture

I have been looking (and will continue to look). Some of it is indeed lacking - but I will make specific notes on what troubles me - or what information I can't find.

I started writing my own description of how drupal works - but found this and stopped writing (why re-invent the wheel): http://iowa.weblogger.com/2004/07/22

I've e-mailed this developer and he said he will be submitting information to the documentation.

andre