Quick peace of mind question

Depends on how paranoid you are Even if you set up your own, there's no telling how theirs will be set up. I've seen people';s sessions get goofed cos the sysadmin had cookie caching turned on. 

 

It's been my experience that the app runs the same with apache+mod_proxy_balancer as with nginx.  That said, most companies I know of try to have a staging server that mirrors their prod server. This helps eliminate any questions as to whether it's the machine / os / server / size of the hamster in the CPU.

 

Could also compromise... use apache';s regular proxy to bounce requests over to nginx

 

On 10/17/07, Vince W. < ruby-forum-incomingandreas-s.net">ruby-forum-incomingandreas-s.net> wrote:

I usually develop using nginx/mongrel and deploy on the same platform.
In the past I'd develop on webrick and deploy on lighttpd and would
(rarely) run into situations where code worked on webrick but not on
lightty.

Now I'm in a situation where the client has requested Apache/Mongrel
while I'm developing on Nginx/Mongrel. &nbsp;Since the Rails side is handled
by mongrel, is there any chance that the front-end webserver difference
will cause the code to act differently? &nbsp;If so I'll probably just set up
another dev environment to mimic the deploy platform.

cheers,
Vince
--
Posted via http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Deploying Rails"; group.
To post to this group, send email to rubyonrails-deploymentgooglegroups.com
To unsubscribe from this group, send email to rubyonrails-deployment-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---