I'm trying to learn some basics of Ruby on Rails and encountered a problem : my Rails project seems to work fine with Firefox but nothing is shown with Safari?
I also tried this with a new project :
rails emptytest
cd emptytest
script/server
Producing output:
=> Booting Mongrel
=> Rails 2.3.5 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
With Firefox, the Rails default page was shown, with Safari nothing was shown (no error, "Page source" was also empty).
Hmm... While still writing this, I found the thread Rails 2.3 just serving Firefox which adviced to upgrade mongrel (the web server); for some reasons Rails 2.3 and old versions of Mongrel would not work well together.
sudo gem update mongrel
After that, rails pages were shown as supposed with Safari also.
I'll write this down here if somebody ends up in the same situation. (I didn't found anything relevant with tags ruby-on-rails + safari)
As mentioned in the question, upgrading mongrel solved the problem.
Related
I'm new to Ruby on Rails, and am trying to set up a basic, local web server in order to dive into all the framework has to offer. I've installed rails using
gem install rails
and have everything seeming to work. However, I also downloaded rails 5.0.0.rc1. When I call to boot up the server with
rails s
or
bin/rails server
it just ends up with a blank screen on http://localhost:3000. Does this have anything to do with the installation of rails 5.0.0.rc1? Why am I just getting a blank screen and not the default information page which signals that it is working?
WEBrick usually writes its output to both development.log and stdout. However it suddenly stopped doing so and it is not writing to stdout. All we're getting is
Booting WEBrick
=> Rails 3.2.8 application starting in development on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
and then nothing. development.log seems to be written to properly.
This is a project-specific problem because it's happening to all members of our team in different computers. On the other hand if I create another Rails project (and copy the Gemfile and Gemfile.lock to ensure I have the same gems) I get the normal output on the terminal.
This is a big problem because among other things it prevents us from using pry or ruby-debug since I have no access to the process on a breakpoint.
We're using Ruby ruby-1.9.3-p194, Rails 3.2.8 and WEBrick 1.3.1. In case it matters we're all on Macs (Mountain Lion).
Any ideas what could be causing this and how to solve it? We need stdout back! Thanks
It turned out that someone had added these three lines to config.ru
log = File.new("console.log", "a+")
$stdout.reopen(log)
$stderr.reopen(log)
It was very painful to figure out this one, so needless to say, don't do that.
If you use pry-remote you should be fine.
I'm trying to learn Ruby on Rails. When I build my app and try to run the server with rails s I get the following:
**radu#radu ~/rails_projects/first_app $ rails s
=> Booting WEBrick
=> Rails 3.2.6 application starting in development on http:// 0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2012-07-06 15:30:09] INFO WEBrick 1.3.1
[2012-07-06 15:30:09] INFO ruby 1.8.7 (2011-06-30) [i686-linux]
[2012-07-06 15:30:14] INFO WEBrick::HTTPServer#start: pid=8179 port=3000**
Then it stops for no apparent reason and T can't do anything except close it with ctrl+c.
What can I do to fix this?
rails s runs the web server that ships with rails. All that does is sit in the background as a process and listens for incoming web requests on port 3000 on localhost. Run it again and go to http://localhost:3000.
Are you expecting more of a console where you can interact with your application? If so, what you want is rails console which allows you to interact with your app. You can write and run code - really useful for trying out things on the fly before you commit them to code in your app.
Are you really expecting a magick in rails. Open the browser and open localhost:3000, come back here and check the logs. You need to hit the server in order to get the logs and this is how it works.
total n00b question here but I can't seem to find the answer searching around here or the web.
I have Ruby v1.8.7 (2009-06-12 patchlevel 174) and Rails v.2.3.5 installed on my Mac (10.6.8). I have no problem generating a Rails directory and starting the Ruby server, but what happens is that once the server is started I have no prompt and no code I type seems to execute.
to be specific - here is the terminal code from a session:
bvb:new bennettvonbennett$ ruby script/server
=> Booting Mongrel
=> Rails 2.3.5 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
after this point there is no prompt and no command I type seems to produce a result.
what am I doing wrong?
This is the correct behavior. You're not doing anything wrong.
The server runs in the foreground so that you can see the log output on every page load without having to open a specific log file. It's very helpful for debugging and staying aware of what the code you write does to the application and the database.
To return to a normal command prompt, you can send an end-of-text character (usually ctrl-c) to stop the server. Most of us Rails-folk work with multiple terminal windows open - server running in one, and others for other functions, such as the rails console, started with
ruby script/console
which will let you experiment with other Rails controller functions, much like irb for standard Ruby.
With ruby script/server you launch the webserver. Run ruby script/console if you want to execute commands against your current Rails application.
You're loooking for:
script/console
If you want to play with your project in a console.
My client wants me to download a working ruby on rails project to my local system. But when I connected to a server, I got nine identical project folders (which seem like different versions). Is there a way to know which project is running using process id (I have only the process id)?
If you have the process ID, then check /proc/[pid]/cwd symbolic link. This is the process' current directory.
I assume that you are on a Linux-like system.
If you are not, then you may issue a HTTP request (to wake up the rails app) and then look which logfile has been modified recently.
if you are able to run rails console on your server then type this: Rails.root in your console or irb it will tell that project you are on belongs to which directory!
no we cant know using process id. but when you start server you will find rails version like
:> ruby script/server
=> Booting Mongrel
=> Rails 2.3.10 application starting on http://0.0.0.0:3000
above line using rails 2.3.10 version and if you want to know ruby version simply call
ruby -v in your command prompt