> I would have guessed that a big issue with Django from an enterprise > perspective is its use of 'singletons'. > > How much is this an issue in practice? Yes, that's been my experience. For complex deployments with tens or hundreds of apps, it is often the case that it is absolutely essential to have settings on a per-app basis. Unfortunately those settings very often clash.
> It strikes me that this is just one example of a whole class of "best > practice" stuff that we should document, but don't at present - like > project layout, automated deployment, continuous integration, > configuration management, etc. It would help smaller companies I think, folks who need to deploy a couple of SOA nodes or a site with ten or twenty apps across a handful of servers. When it comes to huge deployments, it is so diverse. Best practice for Google isn't best practice for wisconsinhairstylists.com Case studies are helpful if folks can share them. But its a political minefield (or unhelpful pontification, depending on the care you take) to get into the business of canonizing deployment structures!
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
