convore.json/groups/django-community/user-defined-subdomains-with-djangoapache/messages.json

[{"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303144875.87643, "message": "what\u00b4s the best way to do something like campaignmonitor does with customers? every user has a specific login-page (like myusername.createsend.com).", "group_id": 81, "id": 727908}, {"user_id": 1736, "stars": [{"date_created": 1303326501.548177, "user_id": 11547}], "topic_id": 20128, "date_created": 1303145069.120708, "message": "As a random guess, a wildcard DNS entry and ServerAlias, and a middleware that converts the URL to something more easily routable.", "group_id": 81, "id": 727933}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303144884.8964691, "message": "found this one: http://www.rossp.org/blog/2007/apr/28/using-subdomains-django/", "group_id": 81, "id": 727910}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303144946.7332571, "message": "btw: we\u00b4re using mod_wsgi", "group_id": 81, "id": 727915}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303145521.656477, "message": "thanks, DNS/alias is obvious. I\u00b4m more concerned about handling it on the django-side. thought about a decorator, but a middleware is probably a better idea.", "group_id": 81, "id": 728003}, {"user_id": 7129, "stars": [{"date_created": 1303248186.2624669, "user_id": 16171}], "topic_id": 20128, "date_created": 1303146167.910331, "message": "https://github.com/playfire/django-dynamic-subdomains/  also takes the decorator approach and also some utilities that make constructing domain-based URLs nice and avoids having to hack /etc/hosts locally. ", "group_id": 81, "id": 728229}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303147811.2120769, "message": "will definitely check that out ... thanks. unfortunately, the docs are missing.", "group_id": 81, "id": 728538}, {"user_id": 13912, "stars": [], "topic_id": 20128, "date_created": 1303149891.519639, "message": "regardless of what deployment method you are using you'll get the requested domain in the 'host' header of the request. You'll just need a wildcard domain to point to your server's ip and set the virtual host on your webserver as a wildcard domain. After that it largely depends on your whole usage scenario. Maybe you'll want the host to be passed as an argument to every view, or just make it easily accessible as a property on the request. Also you may need to provide a custom auth backend so that certain usernames can only log in at certain subdomains.", "group_id": 81, "id": 728855}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303152396.5697851, "message": "this may seem a dumb question, but ... do I need a seperate vhost for the wildcard domain or can I use the already given vhost?", "group_id": 81, "id": 729281}, {"user_id": 17897, "stars": [], "topic_id": 20128, "date_created": 1303152594.0040259, "message": "that really depends on whether the vhost is setup as a wildcard vhost or not.", "group_id": 81, "id": 729295}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303152678.0296221, "message": "setting up a different vhost has been the proposal of our server-managers. on the other hand, it\u00b4s our server ... so yes, we can tweak the config.", "group_id": 81, "id": 729317}, {"user_id": 17897, "stars": [], "topic_id": 20128, "date_created": 1303152628.9355459, "message": "or if you have the possibilities to tweak the config of the vhost so that it does accept the all the reqeusts to *.yourdomain.com", "group_id": 81, "id": 729303}, {"user_id": 17897, "stars": [], "topic_id": 20128, "date_created": 1303156041.2969539, "message": "having dedicated vhosts which server fixed hosts like www and what not plus a separate one for the wildcards is probably a good idea though.", "group_id": 81, "id": 729894}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303156171.9544261, "message": "why? performance? easier setup/maintenance?", "group_id": 81, "id": 729933}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303156399.71035, "message": "besides, let\u00b4s say the app is on my main vhost and I have another vhost for the wildcard-domains ... how am I able to use my app on the second vhost? or do you suggest to split the app to different vhosts? sorry if this is confusing.", "group_id": 81, "id": 729998}, {"user_id": 17897, "stars": [], "topic_id": 20128, "date_created": 1303157974.7398291, "message": "well I was assuming that the fixed domains would run something different. If that is not the case then one vhost would be better. My thinking was along the lines of if someone manages to register the user www. That wouldn't be to cool. :) If you were running www of a separate vhost then that wouldn't be a problem.", "group_id": 81, "id": 730476}, {"user_id": 18655, "stars": [], "topic_id": 20128, "date_created": 1303158070.8457, "message": "thanks for the clarification. guess I\u00b4ll go with one vhost for now \u2013 just need to make sure about the reserved prefixes (like www and others).", "group_id": 81, "id": 730514}, {"user_id": 12817, "stars": [], "topic_id": 20128, "date_created": 1303295682.3229051, "message": "I've done something similar to this using a middleware that switches the urls.py according to whether it's a user-defined subdomain or not (urls.py for the main site, and user_urls.py for user subdomains), and if it is, adds the subdomain as a property to the request.", "group_id": 81, "id": 753588}]