From: Greg Donald Date: 2006-07-27T02:45:00+09:00 Subject: Re: eRuby: A tutorial on using Ruby on the web On 7/26/06, tesla wrote: > Rails on my PC has differences from what is in my web host and so the > application will not run without me tweaking it. We deployed a test app to > Dreamhost, Bluehost and HostPC. Of the three Bluehost worked without > problems but still required some changes. The other instances just did not > run. That's why there are different environment files in config/environments. You can customize your setup based on the environment. > The problem is that they all hosters seem to have unseen differences that > clog the process. Each of the three we tried seem to have different versions > and packages of Ruby running. That's how it is everywhere. One of my client's setups will be running PHP 4.4.x while another will be running PHP 5, one has MySQL 3.23 and another has 5 already. As a developer I assume it's up to me to write code for the production environment. I then try to duplicate that exact production environment locally if possible. With apps like VMWare and Parallels and FreeBSD jails, it is quite simple. > Apache was a problem. We run Apache 2 which > did not seem to be a problem a first but when things stopped working > everyone started pointing to the Apache servers first. My setup uses Apache 2 proxying requests to a Lighttpd instance. I never have to mess with Apache when troubleshooting my Rails apps, I just do the fix and restart my Lighttpd instance, since it runs as my user, not Apache's user. > Rails was just not > generic enough for us. I'm sure it can handle a 15 minute guestbook app. :) > SSH seemed to be needed to troubleshoot. Each time we contacted a support > desk we were asked to telnet into the server and do configuration changes. Interesting that you would choose a host that still allows telnet, very insecure. > Exactly our point. Since the end result should be a Ruby teaching > situation we found that Rails got in the way. Also students would need > two books (budgets you know) rather than one ;) Well.. when the docs aren't all that great and the Rails developers mostly write books instead of improving the online docs, what's a developer to do? Buy the books. *shrug* I feal your pain on this one. I have 8+ years doing PHP and MySQL apps and have never had to buy a single book. Meanwhile I have slightly more than a year doing Rails apps and have 5 Ruby/Rails related books, not counting ebooks. > Also I truly dislike that acronym FUD. It is thrown about too often when > people are giving their experiences, outlook and opinion. None or us fear > Rails, are uncertain about its purpose nor doubt that its capabilities. We > just decided based on our own conferencing and experimentation not to go > with Rails this time and we gave our reasons why. Ruby and Rails and command lines and sysadmin tasks aren't for everyone. Good luck. -- Greg Donald http://destiney.com/