I work with http://www.djangoproject.com/ and wish to install my django sites under IIS, but not figure out how.

Please share how do this to update my ticket in this issue at http://code.djangoproject.com/ticket/2039
 

But I’d have to agree with MaryAnne as well – I’m more comfortable in Linux than Windows, but I have yet to see anything on the *nix side that stacks favorably against Active Directory.

If all you’re looking for is an LDAP server to authenticate against, that is one thing. But if you’re looking to authenticate thousands of users on a campus or a hospital or a base – or, for that matter, millions of people online – complete with profiles, ACL policies, and services; you really can’t beat Active Directory, especially with AD’s tight IIS integration… unless you know a program I don’t – in that case, please let me know!

AS for the MS Patent Controversy – no need to resort to Google, NeoSmart Technologies has been on the forefront of that controversy, blogging about it right here with hits coming in from all over the web (Digg and Slashdot included): http://neosmart.net/blog/2007/microsoft-linux-patent-violations/

As for the Linux server it blows M$ out of the water to no end. If your a programmer you can fix the bugs upload it and have it available for others. With M$ if there is a security hole, its usually there till M$ decides to release a patch. So basically I paid several dollars to a company to get a server with security holes and have to wait to get the patch. Seriously M$ is a joke on the server end.

Now M$ on the desktop wins hands down. To update linux desktop it can take awhile making sure you have the right libraries and packages and can be a pain. It is only for advanced users for which I am guessing your not.

As for Linux hurting Windows, google “Microsoft Linux software patent” M$ is trying hard to hold on to what they have. Mark my words. They will sue. Its their only option.

you can still choose to subcontract.

> You can shift everything to Linux, but that software is already
> bought and paid for, the configuration in place, the web servers
> all up and running just fine.

even after proprietary software is bought and paid for it still costs more than Free Software.  one of the more significant ways in which proprietary software costs more is in the time it takes to jump through various hoops and engaging in redundant research to make things go.  proprietary software vendors in the end are looking to insure they can make money selling their software.  whereas most cooperatively produced Free Software applications are focused first and foremost on doing the job they were designed to do–well.

another nice thing about Free Software is that you are much less likely to find that the application that you are relying on goes away at some point.  so the time you invest in becoming proficient with Free Software is *much more* likely to retain it’s value than the equivalent time invested in a similar proprietary solution.

 – david 

That’s an interesting idea there…. But i have to disagree.

I mean, just look at how many holes were reported for IIS 5 (with Windows Server 2000) and even Windows XP…

http://secunia.com/product/1438/ – A total of 3 vulnerabilities in 5 years almost!

http://secunia.com/product/73/ – 33 vulnerabilities there.. But that’s not the interesting part.. what i find most intriguing is that of the 33 vulnerabilities, 9 remain unpatched!!!

At NeoSmart Technologies we chose to use Windows and IIS, because we truly believe that IIS is a great web server.. Unlike its predecssors, IIS 6 is fast, stable, light, secure (less reported vulnerabilities than Apache), and very capable.

But in your example, you were the man at the top. What if you’re newly hired at a company that has 100 servers already running Windows and IIS – and your predecssor left?

You can shift everything to Linux, but that software is already bought and paid for, the configuration in place, the web servers all up and running just fine. In that case, the better thing would be to swallow that bad taste creeping into your mouth, open up Opera (or Firefox if you prefer) to this very page, and get tuning!

“Whether you like Windows or not, at some point or the other, you may find yourself using IIS”

actually, it’s possible to always choose other solutions.  the reason, because you are always at choice (although sometimes you may not recognize that fact).

take for example my case.  i’ve told my clients unequivocally that i will not administer IIS for them.  if they insist then that work will be subcontracted.

i chose that.  might there be repercussions?  certainly.  what’s the worst that possble repercussion?  losing a client.  ok, i’m willing to suffer that repercussion.

others may not be willing to suffer that repercussion.  this is still a choice.  however, people often fail to recognize this as a choice and instead perceive that they “have to” because they want the monetary reward.

it’s way more helpful, in my experience, to clearly acknowledge the repercussions of my choices and what the needs are behind these choices.  doing so allows me to come from an empowered place rather than a dis-empowered place.

a hypothetical example:  “i’m working on IIS even though i dislike supporting microsoft because i have 5 kids and i enjoy being able to feed them supper.  it’s my intention to shift to working on Free Software web servers because i enjoy the cooperative communities that exist around those applications.  during the evenings i’m going to work hard to become proficient with the applications i prefer so that i can make the shift to using them and still feed my kids supper.”

what this example shows is that when you acknowledge you are at choice you are then better able to make different choices.

compare the above example to this one:  “god, i hate working on IIS and i don’t have a choice.  microsoft rules the IT world.  i have a mortgage to pay off and i’m not very skilled with apache.  i’m completely trapped in this god-forsaken job.”

see the difference?

take what i offer with a grain of salt.  if you like it, keep it, otherwise ignore it.

peace,
david

And if you use IIS – PHP is fucked.

Thanks for this guide, I’ll be checking out MSoft’s FastCGI fix – thanks!