On 21/07/2006, at 7:49 AM, Brian Hamman wrote: are you talking about the data itself, or the code? If your app requires sharing of data, you should probably think of using sites as a many-to-many field instead of as a foreign key. but this will cause a lot of upheaval in your code when you are doing retrieval. if it's the code just stick it in a common place and put it in your python path. Hugo has his 'stuff' directory. I have zilbo.common it isn't a big deal.. it all works.
what I do is have a site specific folder in my template path which overrides any project-specific ones. that way if site #4 wants to do something crazy it goes in site_4_templates/. Ian -- Ian Holsman http://economychat.com discussion on the economy and economics in general --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~--- |
- Re: shared apps accross multiple sites/projects Ian Holsman
- Re: shared apps accross multiple sites/projects Jacob Kaplan-Moss
- Re: shared apps accross multiple sites/projects Brian Hamman