Regarding the sub domains

[anup kalburgi]

Hi,

We have multiple users and each user needs to have a subdomain along with a separate database for each one of them,

Like moris.example.com      .....  to have a database by name moris or something like that,
and so on for different customers.

Having multiple databases is necessary because of policy they have.

What is the best approach to do this, i just saw many discussions on stackoverflow, where they said having such a set up is not advisable. But here i cant really go with it.

What is the best way to go about this? Please advice.



Thanks



--

[m1chael]

step #1 would be to configure your name servers to resolve anything.example.com to an ip

--

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

[Christopher Hartfield]

You would have to yes first configure your name servers and allow your website example.com to resolve each of those subdomains.  So hopefully your number of users won't be too high :(  If your allowed you might find it easier to do example.com/moris/, but I would assume you can't do that.

Setting up multiple databases isn't too hard and you can use RAW SQL to help you with it. 

Django can handle subdomains with certain plugins like: http://django-subdomains.readthedocs.org/en/latest/index.html

But you still have to configure the name servers.  

So your goal would be to sign up a new user and then make a database for the user, add the tables and insert into the tables

Django supports multiple databases (but I'm not sure you can use Django to create a new db on the fly):

https://docs.djangoproject.com/en/dev/topics/db/multi-db/

Hopefully this gets you started

[creecode]

These comments are for the OP, I'm just using Christopher's message to key off of...

On Saturday, October 13, 2012 10:59:56 PM UTC-7, Christopher Hartfield wrote:

You would have to yes first configure your name servers and allow your website example.com to resolve each of those subdomains.  So hopefully your number of users won't be too high :(  If your allowed you might find it easier to do example.com/moris/, but I would assume you can't do that.

For your name server you'll want to use a wildcard.

Django can handle subdomains with certain plugins like: http://django-subdomains.readthedocs.org/en/latest/index.html

You don't have to use a Django app to handle subdomains, all the routing can be handled with your webserver (like Apache, etc.)  It just depends on where you want to do your configuring. 

 

Setting up multiple databases isn't too hard and you can use RAW SQL to help you with it. 

 

Django supports multiple databases (but I'm not sure you can use Django to create a new db on the fly)

You can get Django to create a new database on the fly with the use of a custom management command.  Essentially you'll be using RAW SQL in the management command to do the database creation bit.  Keep in mind that you need to have a Django environment setup to use the custom management command.  That involves some overhead which only you'll be able to determine if it is appropriate for your situation.

You may want to read this thread on one way to do mass hosting if you're going to use mod_wsgi.

Toodle-loooooooooooooo

creecode