Interesting! So, that means you can serve blog.example.com and shop.example.com from the same server? I haven't tried any of the multi-site support in django, so not sure how this compares. Makes my head hurt to think what this does to SSL. I've never been able to figure out SSL and virtual hosting on Apache.
Brian Schott bfsch...@gmail.com On Jan 10, 2012, at 6:01 AM, Cal Leeming [Simplicity Media Ltd] wrote: > I've hit this same problem myself many times. > > Ultimately there is never any one answer - you can split out functionality > into individual modules, but there has to be a good use case for it, > otherwise the overhead has a negative impact. > > You also have to take into consideration the re-usability of what you are > splitting out, and if something is split out, then it has to be treated as a > standardized module which is kept backwards compatible for everything. > > It's not just a case of having a standardized directory layout, the entire > use case of the project will determine the layout - you can follow 'sane > principles' such as naming convention etc, but the actual splitting of > functionality is really up to the developer (and isn't really something that > can be taught - it's more of an experience thing). > > Personally, I found that using 'MultiHostMiddleware' has been an absolute > life saver for splitting out sites within a single project - check it out: > http://code.djangoproject.com/wiki/MultiHostMiddleware (I just went and > tidied it up a bit). > > Just my two cents worth! > > Cal > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en.
smime.p7s
Description: S/MIME cryptographic signature
