On Nov 30, 6:30 am, "Leon Yeh | New Avenue.net" <[EMAIL PROTECTED]>
wrote:
> Thanks Graham,
>
> The problem is how to automate the database creation at the sign up.
> Also how to keep share one project/ source for all of the instances.
> Multiple settings for each project/ database.
>
> I don't think it is that simple. I have spent couple days look into this
> and have not found any thing that I would considered optimal solution.
What hosting mechanism are you trying to use? I don't regard the
hosting side as that hard. The issue I guess is your expectations as
to whether restarting the web server to add a new virtual host is
acceptable. Also, are you expecting each Django instance to run as a
separate UNIX user, or whether they can all run the same user as long
as each gets their own process.
For database side, if you are just creating multiple instances of same
application. Could you just copy contents of a preconfigured database
to new database name. Worst case is needing to do a few SQL updates to
change virtual host name specific information.
Answer the bit about hosting and how you want to run it, then can
possibly outline a solution.
Graham
> Somebody must have seen this problem before and could have solved it. I
> am going back to see if pinax project has something like this.
>
> Anyhow, back to my research.
>
> Leon Yeh
>
> Graham Dumpleton wrote:
>
> > 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
-~----------~----~----~----~------~----~------~--~---
