We're getting ready to do a major overhaul of our newspaper's website, so we've been looking into some development frameworks. I'm pretty sure we're ready to switch to Django.
Our current site has run on ASP/SQL Server for years. We run a pair of Windows servers for load balancing, connecting back to a local database server. We develop locally; changes trigger a batch copy up to the live site. That's the way it's always been done, and I'm not sure how excited our IT department is going to be if we talk about change. They just purchased three tricked-out Dell servers and their assumption was to continue with the same technology and deployment. They didn't ask us for any input, unfortunately. >From the documentation I see that Django loves Apache/PostgreSQL best, so my first choice would be to persuade IT to set up the new servers this way. It's possible, however, that this will be a deal-breaker because they won't want to maintain a separate OS (everything else is Windows). And I see in the docs that it's possible to run Django on Windows servers as well. So I'm left with a few questions. -- How much stability/efficiency do we lose by running Django and PostgreSQL on Windows? (If it comes to it, is Apache worth a big fight?) -- Is it possible to run a mirror configuration for load-balancing, like we do right now? Does it even make sense to do that? I'm also assuming from the documentation that staying with SQL Server 2005 is not an option if we want to use Django. (Not that I want to, but if I'm wrong could someone please correct me.) Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
