Quote:
Originally Posted by Neko
Hah..I wrote a Poker Paradime hand history scraper for a 2+2er a couple years ago.
So I am building a medium sized Django intranet site at work that is going to replace a whole whack of ad hoc Excel spreadsheets and applications. It's going great so far and everybody is very excited to get it up and running.
I have a fair bit of experience running Django apps with nginx/Apache in Linux and that would be my preferred (and in fact the Django communities preferred) method of deployment. There will be less than 100 users of the application and I know this could be done very cheaply with modest hardware.
However, due to factors beyond my control, we are being forced to use IIS & SQL Server. It is possible to run Django on IIS but it's a bit hacky and certainly not ideal.
Anyways the IT department gives us a quote of over $13000 (!!!) for a dual core, 4GB RAM server with Windows Server, IIS and SQL Server.
Can some of you with Windows server experience tell me if this is totally insane or not? I don't have a breakdown of the costs, but will most of this be from software license costs?
FWIW it's probaby $11000 more than I would have estimated for an equivalent LAMP setup.
Go to some manager, tell him you could get this setup for 2k and he'd save 11k. Also tell him you're the developer and this cheaper setup is actually the best.
I guess your IT staff is just lazy and they only know Windoes/IIS/SQL Server and can't be bothered admining other stuff? This happens a lot and costs companies soooo much money from my experience.
Maybe you can offer to support the server yourself for 5k/year if IT doesn't want to do it lol.
At the very least you should outline that you could still go Apache/MySQL|PostgrSQL without the L if they don't want to support Linux.
Quote:
Originally Posted by MrWooster
Has anyone been following the GitHub security issue? To be fair, its more of a Rails fail (FRails ), but an interesting read. Goes to show that nothing is really safe. Just lucky that no one injected malicious code.
https://github.com/blog/1069-respons...closure-policy
Yep, followed it very closely. You probably could have made a couple millions if you were ethically questionabl just using this info and applying it to all sorts of live Rails systems.
Last edited by clowntable; 03-07-2012 at 05:59 PM.