That's a cunning plan, nice one Andy!
I'd use that if I did it again - a virtual host instance per subdomain
uses lots of memory on a VPS...
Tim.
On 29/12/10 18:19, Andy Shaw wrote:
Tim's solution would obviously work, but it sounds to me like you would
need to manually configure a subdomain
Tim's solution would obviously work, but it sounds to me like you would
need to manually configure a subdomain (including a copy of settings.py)
for each user. Widoyo's solution (or rather, Ross Poulton's linked
solution) would also work but requires quite a lot of boilerplate code
in your view
I did this with one settings.py per subdomain, using the sites
framework. So each settings.py had a different SITE_ID.
Here's how to limit admin to a given user's records:
http://drumcoder.co.uk/blog/2010/oct/02/user-specific-data-admin/
This helps with droplists in admin:
http://drumcoder.c
May be this link will help you:
http://www.rossp.org/blog/2007/apr/28/using-subdomains-django/
Widoyo
On Dec 23, 11:29 am, Parra wrote:
> Can someone give me some tips on where to get started with this ??
>
--
You received this message because you are subscribed to the Google Groups
"Django
Hello,
I'm new to Django and thinking of using it for a project.
In this project, there will be accounts and each account will have a
subdomain.
Based on the subdomain/account, the user will just see the records
that belongs to them.
The tables will be unique for all accounts, so there should be
5 matches
Mail list logo
