Hey Tkm,

Basically this application follows the Basecamp model. A company signs
up for a sub domain, and many users are able to access it. It would be
all in one project, but the sub domain would access a different url.py
so that different applications and views can be used.

Let me know if that helps,

Levi

On Mar 31, 4:02 pm, "Bruno Tikami" <[EMAIL PROTECTED]> wrote:
> Hi vemon,
>
> when the user access user.domain.com the request will be treated by a
> different project or all users share the same project? Though it may look a
> stupid question, if they have separate projects, you don't have to worry
> about it, cause they'll have different urls.py files.
>
> If they share the same project, I can't help you. BTW, I don't even now how
> to share the same project with several sub-domains (using apache).
>
> Regards,
> Tkm
>
> On Mon, Mar 31, 2008 at 5:39 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
>
>
>
>
>
> > Hi guys.
>
> > I'm developing a system that gives a user a sub domain for their
> > account.
>
> > I found this article,
> >http://www.rossp.org/blog/2007/apr/28/using-subdomains-django/,
> > which is really helping. But the problem I'm having trouble thinking
> > through is how I could give sub domains certain urls that the main
> > domain wouldn't have. For example:
>
> > A user's account would be user.domain.com. When they access that it
> > would redirect to user.domain.com/login. I don't want the normal
> > domain.com to be able to go to /login without being a sub domain.
>
> > Ideas on how I should implement this would be great.
>
> > Thanks,
> > Levi
>
> --
> []s!
>
> Tkmhttp://djangopeople.net/brunotikami/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to