I’d like my local hosting company to consider Ruby on Rails as a hosting
platform that they sell and support.
How do I make RoR support “official” to the outside world? If I can get
RoR working on my laptop, I shouldn’t have too many problems getting it
to work in RedHat Linux, right?
Now, this may be a loaded question.
However, I’m nerdy enough to get Rails working on a dedicated Redhat
machine, and just about anyone reading this forum is as well.
That said, if I got Rails working on a dedicated server at this company,
when would I be able to convince them that their hardware/software is
indeed “certified” for the Rails community?
Hi Paul,
Paul L. wrote:
How do I make RoR support “official” to the outside world?
if I got Rails working on a dedicated server at this company,
when would I be able to convince them that their hardware/
software is indeed “certified” for the Rails community?
What’s your motivation for wanting to do these things?
Just wondering…
Bill
Bill:
This particular ISP server is local - something of keen interest to my
app. I’d like the peace of mind knowing that I can drive downtown to fix
something should a server go down.
Will this happen? Probably not. But if the server is on the other side
of the country I’m out of luck.
On 8/28/06, Paul L. [email protected] wrote:
This particular ISP server is local - something of keen interest to my
app. I’d like the peace of mind knowing that I can drive downtown to fix
something should a server go down.
Will this happen? Probably not. But if the server is on the other side
of the country I’m out of luck.
If you’re providing your own tech support why does it matter if the
ISP is “certified” or not? I think that part of the disconnect here
is that I have no idea what you mean by “certified.” Certified for
what?
– James
On 8/29/06, Guest [email protected] wrote:
Certified was a bad term to use. End result: “This host plays well with
Rails.” That’s all.
DreamHost, for example, supports Ruby, but I’ve had half a dozen
problems that are completely separate from problems with my app. So true
Rails “support” is a bit if a misnomer.
To rephrase: “What do you need to feel comfortable about moving Rails to
a host?”
Sounds like you just need a good host. I’m sure there are different
levels of service no matter where you go.
I have been hosting my Rails apps with OCSSolutions for quite a while
now. They have been completely helpful at every turn. They develop
Rails apps from what I understand so they know what is required for a
good Rails hosting environment.
–
Greg D.
http://destiney.com/
Certified was a bad term to use. End result: “This host plays well with
Rails.” That’s all.
DreamHost, for example, supports Ruby, but I’ve had half a dozen
problems that are completely separate from problems with my app. So true
Rails “support” is a bit if a misnomer.
To rephrase: “What do you need to feel comfortable about moving Rails to
a host?”
On 8/29/06, Brian H. [email protected] wrote:
Unfortunately, there’s little that can be done about
developers on your server who write sloppy code which kills the server.
I disagree. At OCSSolutions each Rails app runs under it’s own
user-owned Lighttpd proxied under Apache. Process quotas per user do
the rest.
–
Greg D.
http://destiney.com/
Dreamhost’s problems are related to
- running FastCGI in dynamic mode
- running FastCGI in develoment mode by default
- A process watchdog that kills off FastCGI dispatchers when it
shouldn’t
- Developers who use Dreamhost as their own playground
I have dealt with 1-3 above. 4 is common on any shared host.
All a host needs to do is set up the web server properly and Rails will
play
quite nicely. Unfortunately, there’s little that can be done about
developers on your server who write sloppy code which kills the server.
Sounds like a nice host. I could still see Apache being taken down by
some
php or perl nastiness but at least the process quotas help.