I'm trying to get the to_prepare event to work on a new Rails 3.2.1 project. I've placed the following:
Rails.application.config.to_prepare do
puts 'here i am before a request'
end
into an initializer under config/initializers. According to the documentation here, this block should run on every request to the app when running in development mode, and only once in production. I'm working in development mode, and this block does not run on every request, instead it runs only when I boot up the application, and never again.
The following is a sample of output from when I load the app.
rails s
=> Booting WEBrick
=> Rails 3.2.1 application starting in development on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
here i am before a request
[2012-03-02 20:29:46] INFO WEBrick 1.3.1
[2012-03-02 20:29:46] INFO ruby 1.9.2 (2011-07-09) [x86_64-darwin11.2.0]
[2012-03-02 20:29:46] INFO WEBrick::HTTPServer#start: pid=37897 port=3000
When I make subsequent requests, the string 'here i am...' is not displayed, only the regular output from the Rails log. All my searching has only mentioned documentation that seems to tell me to do things this way. Is there anything I might be missing?
to_prepare is called every time your project is reloaded, which since Rails 3.2 means every time you change a file.
refs: https://github.com/rails/rails/issues/7152#issuecomment-8397470
Related
I have recently changed my app to read a model's constants in from YAML files stored in Amazon S3 (set up in application.rb in an after_initialize). This works without a problem, except WEBrick seems to be losing the constants. It works fine when started, but after some time I'll refresh a view and it will report that the constant isn't initialized. There are no errors, and restarting the WEBrick server resolves the problem.
I'd be grateful for any advice.
Rails 4.1.6 application starting in development ..
INFO WEBrick 1.3.1
INFO ruby 2.1.2 (2014-05-08) [x86_64-linux]
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.
I have Ruby v1.9.3 and Rails v3.2.3 on Win7. 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:
=> Booting WEBrick
=> Rails 3.2.3 application starting in development on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2012-04-30 06:25:06] INFO WEBrick 1.3.1
[2012-04-30 06:25:06] INFO ruby 1.9.3 (2012-02-16) [i386-mingw32]
[2012-04-30 06:25:06] INFO WEBrick::HTTPServer#start: pid=2112 port=3000
after this point there is no prompt and no command I type seems to produce a result (including ctrl-c).
what am I doing wrong?
This worked: Im doing a rails tutorial and this was the got me back on track. Ctrl-Pause/Break stopped the server.
I assume you're running rails server to get to this point.
Everything is working as it should. Rails is a web framework and when you run it in server mode it doesn't accept commands from the terminal. Instead Rails listens for web requests on port 3000 and responds appropriately. While the server is running the terminal window is displaying the internal server logs. Visit http://localhost:3000 while the server is running and you'll see what I mean.
If you want some command line interactivity, run rails console instead. This will load up your Rails environment but instead of listening for web requests on a port it'll give you an irb prompt where you can type ruby.
Ctrl-Pause/Break works. "Pause/Break" confused me for a little bit, so if you are new like me it is the key usually next to F12 that says "pause break". :)
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.