• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Ruby site needs to move off-site

B

bobdole369

Gawd
Joined
Jun 27, 2004
Messages
856
Hi all,

Had a web guy build us a web app that is currently hosted onsite. Would like to move this to a web host that has a dedicated machine for us. We currently do our email here. The OS on the in-house machine is Ubuntu LAMP, the dedicated machine is CentOS.

Any pointers on the ruby install? I'm familiar with various Linuces and what not, just never set this thing up from scratch before.

As far as all the controllers and helpers and what not go I plan to simply recreated the directory structure and go from there.

Also there seems to be mongrel running which might be an issue. Any thoughts?
 
Hire someone.

Rails deployment isn't THAT difficult, but there are certainly a lot of knobs and dials to tweak, especially if the application wasn't built to be moved.
 
CentOS/RHEL can be a major pain in the ass running Ruby web servers when it's on a 64-bit installation. When I say "major", I mean "mucking around in the Ruby source code to fix shit that should never have been released" major. At least, that's what I ended up doing just to get RubyGems running about 2 years ago on our production server, due to some bad code which required ZLib but couldn't be satisfied in any way. Took days to figure it out.

That said, it took me about half an hour to set up a Debian machine as a Ruby/Mongrel server, and now it's even easier with mod_rails (http://www.modrails.com/).
 
:LJ: said:
CentOS/RHEL can be a major pain in the ass running Ruby web servers when it's on a 64-bit installation. When I say "major", I mean "mucking around in the Ruby source code to fix shit that should never have been released" major. At least, that's what I ended up doing just to get RubyGems running about 2 years ago on our production server, due to some bad code which required ZLib but couldn't be satisfied in any way. Took days to figure it out.

That said, it took me about half an hour to set up a Debian machine as a Ruby/Mongrel server, and now it's even easier with mod_rails (http://www.modrails.com/).
Click to expand...

The ZLib thing was fixed, there was a bad point release which was fixed pretty quickly.

I wouldn't run modrails on a 64bit machine yet though (Or really much of anything in Ruby), the last release was the first to officially support 64bit platforms, but there continue to be more issues than it's 32bit counterpart. 64bit Ruby tends to take up substantially more memory than 32bit versions, which is a bit of a problem given Ruby's already heavy memory footprint.
 
Sgarissta said:
The ZLib thing was fixed, there was a bad point release which was fixed pretty quickly.

I wouldn't run modrails on a 64bit machine yet though (Or really much of anything in Ruby), the last release was the first to officially support 64bit platforms, but there continue to be more issues than it's 32bit counterpart. 64bit Ruby tends to take up substantially more memory than 32bit versions, which is a bit of a problem given Ruby's already heavy memory footprint.
Click to expand...

Good to know...I tend to run Ruby sites on a bunch of virtual servers these days, which are always 32 bit since adding another VPS is cheaper and more effective than going past 4GB RAM.
 
You must log in or register to reply here.
Back
Top