Drupal for my family - subdomains for each individual?

DaveNotik - February 27, 2005 - 01:51

Hi all:

I've seen discussion of using Drupal with a multiple-domain setup, but I've seen no clear answer to a question I have:

I want to setup Drupal for my family (notik.com), maintain one Drupal installation (which I will administer), yet have individual subdomains for each family member (e.g. dave.notik.com, sol.notik.com...) pointing to their personal blog in Drupal (not just a redirect). I want to have the ability to apply a different theme to each of these blogs so each family member can personalize their blog. The main domain (notik.com) will show individual items that have been promoted to the front page, etc.

Thoughts on how best to accomplish this?

Thanks much in advance.

--Dave

i was working on something like this.

adrian - February 27, 2005 - 01:58

it's possible. but it's a bit of a hack.

--
The future is so Bryght, I have to wear shades.

A stab in the dark.

grohk - February 27, 2005 - 02:24

But you could try to use this howto by bertboerland@www.drop.org to setup the subdomains and then maybe use the Sections module by
Bèr Kessels
to theme the users blogs.

Thanks to Adrian's excellent phptemplate engine, I do have a subdomain for our site setup that switches the main theme to a mobile version when mobile.code0range.net is the url being requested.

Hope this helps.

---
Code Orange: Drink Your Juice

One approach

kbahey - February 27, 2005 - 03:36

You can do it like so:

Each subdomain will have its own conf.php/settings.php file (e.g. dave.notik.com.php for you, sol.notik.com.php for the wife, ...etc.)

Drupal's code and modules will all be the same, but the databases will be separate.

This means each of them can have a different theme.

notik.com can just have links to the individual subdomains.

Of course, there is a bit of an overhead here, since you are administring several Drupal instances that share the code.

Another approach is to use the subdomain as a redirection mechanism. For example, in .htaccess, you set dave.notik.com to redirect to notik.com/dave where this is a path alias to a category.

Then you can use sections to theme each category separately.
--
Consulting: 2bits.com
Personal: Baheyeldin.com

The hammer is not the only tool

earlax - March 2, 2005 - 14:59

Have you considered using Aliases in Apache?

I'm sure there are other ways to do it, but this could even be automated if you were scripty.

Tatu Ylonen, SSH 1.2.12 README: "Beware that the most effective
way for someone to decrypt your data may be with a rubber hose."

New advice, post 4.6?

DaveNotik - May 10, 2005 - 05:02

Hi all:

Now that 4.6 is out, with multi-site support, I thought I'd inquire on this issue again -- sorry for any redundancy.

I set up 4.6 at www.notik.com, for starters. I want to have dave.notik.com, sol.notik.com and more have their own blogs and their own themes, with the ability to promote certain things to www.notik.com.

What's the best way? Multiple sites, or one site with the subs pointed to the respective blogs? One database, or prefixes? ...

Hell, in a great world I'd like for each individual to have their own blog, but more... like blocks with their own lists, pages of their own, albums, lists, their own little world. Then www.notik.com could be it's own area democratically authorized to feature content from the individuals.

There are 7 kids in my family, and we all want to express, but have a general area to serve as the portal of sorts. I think we're the perfect test case.

Anyone have any thoughts/suggestions?

Thanks!

--Dave

You're not talking multi-site

Boris Mann - May 10, 2005 - 06:36

Multi-site is multiple, independent sites -- it makes it easy to run off the same codebase, but the sites are separate, each with a separate database.

I would do as KB suggested, and have each as a separate site. You can use RSS to aggregate the posts from all sub-sites onto the main site.

There is some funky new stuff coming that will allow content to be published-subscribed directly between sites, but it's not quite done yet.

well

sepeck - May 11, 2005 - 19:04

You could also do this: http://drupal.org/node/2622 and it will work. But you will need to really be careful about the setup and any updates and modules that you add. I did it once on a test setup and it worked, but decided not to. You could also try the Organic Groups module and give each family member a 'group' of their own...... Not entirely sure if it would work for you not having played with it.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

OK Dave, So How'd You Do It??

ajliberty - August 6, 2005 - 20:19

http://www.notik.com/
http://dave.notik.com/

OK, Dave
So let us all know
Which route did you take?

This is the same thing I'd like to accomplish - the simpler, the better. I just would like to add some sub domains.

BTW, my host will only allow one subdomain through their control panel

Thanks

Lib

domain name at url

shunfenghu - May 11, 2005 - 15:55

Hi all,

i am a newbie for OSS and LAMP CMS, however i am interested in this toy. here i have one question - that is what is the difference between http://drupal.org and http://www.drupal.org in URL address bar, for latter i understand it is on the world wide web. for the former i don't quite understand how to make it. and something on subdomain i also would like to learn here. who can direct me to a url and help me understand it clearly. thanks a lot.

shunfeng

they are the same

Harry Slaughter - November 1, 2005 - 06:23

www.drupal.org is just an alias that points to drupal.org. they are the same thing.

the 'www' doesn't indicate anything at all. it's a convention adopted long ago to name machines based on the primary service they provided, like ftp, gopher, www, irc, etc... it's pretty common these days for folks to just use the domain.com format.

--
Living in fear of patch hell?
Want a stable development environment?
Support Dev Releases: http://drupal.org/node/30903
Support Code cleanup too: http://drupal.org/node/28540

 
 

Drupal is a registered trademark of Dries Buytaert.