On Nov 29, 2:34 pm, "Leon Yeh | New Avenue.net" <[EMAIL PROTECTED]>
wrote:
> Hi All,
>
> Usually, when I am working on django project, I have one database per
> web site. So one company has all its database in one single mysql database.
>
> However recently I am working on a site that had requirements similar to
> basecamp web site.
>
> Here are the new requirement:
> 1. Multiple company with multiple users.
> 2. Each company should not be able to see other company data.
> 3. Each company access goes tohttp://companyname.app.com
>
> so my question is that what is the best way doing this ? Should I
> develop the site with:
> a. One database or each company has its own database.
> b. How to handlehttp://companyname.app.comrouting ?
> c. What is the best way of doing the database partitioning if I go with
> one shared database ? Data confidentiality is very important. I am
> afraid that error in database access expose one company data to others.
If data confidentiality is an issue, then keep using separate database
instances for each site. Each web site having their own host name, and
with each application instance in separate processes, is easily
handled with Apache and mod_wsgi (daemon mode), or fastcgi solutions
with web server of your choice that is capable of handling virtual
hosts. Nothing too difficult here.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
