On 2/27/07, C.jay Martin <[EMAIL PROTECTED]> wrote: > > Previously, it was Webrick for me... I expected to have access to apache > with fastcgi when I was developing the project... apparently only > certain purchased apps are allowed to use the apache server... so the > webserver guy gave me the admin pass to the webserver and said "get your > rails app working here". > > I think I'm going to try lighttpd with fastcgi instead, honestly... > It'll mean another midnight, but if I can't get mongrel working..bleh >
I don't know how SQL Server from *nix will for for you, but deploying isn't a thing so simple that "you drop a file here and you're ready to roll". It requires a lot of thinking and often a re-thinking based on the initial results. Often it takes me 3 rounds to get a good deployment environment, without counting DB communication issues. Guess Zed will agree with me on this: If your company is "constrained" to windows environment (that includes IIS), you should find a workaround... hey, you could even add pen [1] to the equation and do some load balancing to a bunch of mongrel via ISAPI rewrite: IIS -> ISAPI rewrite -> Pen (cygwin) -> Bunch of Mongrels. If your decisions have height at your company, use a scenario that makes you feel better, nothing stops you, all we want is that you be happy :-) Your questions are welcome, but ignoring issues regarding DB<->App communication (I guess since you're running just one instance of your application) isn't right. There are things inherent to each solution that you must know (or at least try), even if you coded your app in a "magical" framework like rails. I'm here to contribute and help the community, so feel free to ask :-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
