# Quick peace of mind question

**URL:** <https://www.ruby-forum.com/t/quick-peace-of-mind-question/117526>\
**Category:** Deployment\
**Created:** [October 17, 2007, 6:19pm UTC](https://www.ruby-forum.com/t/quick-peace-of-mind-question/117526 "2007-10-17T18:19:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/b5e925/32.png) [@vince](https://www.ruby-forum.com/u/vince)\
**Post date:** [October 17, 2007, 6:19pm UTC](https://www.ruby-forum.com/t/quick-peace-of-mind-question/117526/1 "2007-10-17T18:19:20Z")

</div>

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. 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? If so I’ll probably just set up  
another dev environment to mimic the deploy platform.

cheers,  
Vince

---

<div class="post-metadata">

**Author:** ![vince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/b5e925/32.png) [@vince](https://www.ruby-forum.com/u/vince)\
**Post date:** [October 17, 2007, 6:33pm UTC](https://www.ruby-forum.com/t/quick-peace-of-mind-question/117526/2 "2007-10-17T18:33:05Z")

</div>

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 🙂