We've run into a pretty annoying issue lately with Django. Being that our site is VERY large, and the codebase has become a framework for the smaller sites, which all run off the same load balanced servers, we began seperating content.
For example: - We have www.curse-gaming.com, which is all the base apps, some templates customized just for this site, a few if statements customized just for this site (such as get abs urls) - We have wow.curse-gaming.com, which is a huge content portal, and includes a database based off of in-game stuff. - We have vg.curse-gaming.com, which will also be a huge content portal, and we've created a database for this one as well. My brilliant plan (from development launch with Django), was to have our root django directory with all the apps like normal, and then any specific apps would be ~/site/appname/. Now, our problem comes in here when we have ~/wow/database/, and ~/vg/database/. Now we access these with cursesite.wow.database just fine, and cursesite.vg.database just fine, and they're on installed apps for only specific configs. Our issues arrise because of content_type's not supporting subdirectories in apps, and same with permissions. We end up with database_app, instead of something like wow_database_app. So, I'm proposing this as a framework change. Any comments? --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
