aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/commands/server.rb
Commit message (Collapse)AuthorAgeFilesLines
* Remove debugger supportRafael Mendonça França2015-01-041-12/+0
| | | | | bebugger doesn't work with Ruby 2.2 so we don't need to support it anymore
* Remove the tmp/sessions folder and its clear taskRobin Dupret2015-01-031-1/+1
| | | | | | | | | | Commit 1aea470 introduced this directory but this was at a time when the default way to store sessions was on the file system under the tmp directory. Let's remove references to it from the documentation as well. [Robin Dupret & yui-knk]
* Document that the default for `rails server -b` has changedGodfrey Chan2014-09-221-5/+1
| | | | Fixes #16578
* fix server names [ci skip]Vijay Dev2014-08-221-1/+1
| | | Per feedback in https://github.com/rails/rails/commit/af63e4a2546629c3fb2d53cffb7d4ea0e8663f68#commitcomment-7477636
* Make text consistent in help text of rails server and console commands.Vijay Dev2014-08-211-9/+9
|
* Add ability to extend `rails server` command options parserAndrey Chernih2014-07-111-7/+11
| | | | | | | | | | | | | | | | | | | | | | | | | With this change it will be possible to add additional options to the `option_parser` like this: require 'rails/commands/server' module Rails class Server < ::Rack::Server class Options def option_parser_with_open(options) parser = option_parser_without_open options parser.on('-o', '--open', 'Open in default browser') { options[:open] = true } parser end alias_method_chain :option_parser, :open end def start_with_open start_without_open do `open http://localhost:3000` if options[:open] end end alias_method_chain :start, :open end end
* Keep debugger support only for rubies < 2.0.0David Rodríguez de Dios2014-04-081-2/+11
|
* AestheticsRafael Mendonça França2013-11-071-13/+13
|
* Move interrupt information to print_boot_information methodAlex Johnson2013-11-071-4/+1
|
* Extract method refactoring for Rails::Server#startAlex Johnson2013-11-071-24/+38
|
* Make logging to stdout work again with implicit `development` envMarc Schütz2013-10-131-1/+2
|
* Only output Server logs in Developmentschneems2013-09-221-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now when you start a server via `rails s`, the logger gets extended so that it logs to the file system and also to stdout. This extension behavior is not "intelligent" and if the default logger is already set to output to stdout, then the contents will be received twice. To capture logs in accordance with http://www.12factor.net/logs some platforms require the logs to be sent to standard out. If a logger is set to stdout, and the server is started using `rails server` instead of another method (i.e. `thin start` etc.) then the app will produce double logs. This PR fixes the issue by only extending the logger to standard out in the development environment. So that in production you don't get double logs like this: ``` ActionView::Template::Error (wrong number of arguments (5 for 4)): 1: <% lang_index = 0 %> 2: <div class="row"> 3: <ul class="nav nav-tabs nav-stacked span2" data-tabs="tabs" id="repo-tabs"> 4: <% repos.group_by(&:language).each do |lang, repos| %> 5: <% unless lang == nil %> 6: <li><a href="#<%= "#{lang.parameterize}#{lang.hash}" %>" data-toggle="tab"><%= lang %></a></li> 7: <% end -%> app/views/shared/_repos.html.erb:4:in `_app_views_shared__repos_html_erb___1685450633638247395_70300668607000' app/views/pages/index.html.erb:13:in `_app_views_pages_index_html_erb__2084723628308867770_70300687584880' ActionView::Template::Error (wrong number of arguments (5 for 4)): 1: <% lang_index = 0 %> 2: <div class="row"> 3: <ul class="nav nav-tabs nav-stacked span2" data-tabs="tabs" id="repo-tabs"> 4: <% repos.group_by(&:language).each do |lang, repos| %> 5: <% unless lang == nil %> 6: <li><a href="#<%= "#{lang.parameterize}#{lang.hash}" %>" data-toggle="tab"><%= lang %></a></li> 7: <% end -%> app/views/shared/_repos.html.erb:4:in `_app_views_shared__repos_html_erb___1685450633638247395_70300668607000' app/views/pages/index.html.erb:13:in `_app_views_pages_index_html_erb__2084723628308867770_70300687584880' ``` ATP Railties. Opened against master in favor of #10999
* add notice to server boot messages if using default 0.0.0.0 bindingLuke Wendling2013-05-251-0/+3
|
* More helpful message when starting serverGabe Kopley2013-03-181-1/+1
| | | | v2 of pull request based on feedback from @rafaelfranca, @schneems, and @carlosantoniodasilva
* config.ru uses the effective Rack appYves Senn2013-03-151-0/+1
| | | | | | | | | | We used to pass the Rails::Application subclass to #run. The Rails server then called #to_app to convert that class to the actual Rack application. if you surround `#run` with a call to `#map` the server no longer convertes the class to the instance and we end up with unnecessary delegation calls on every request.
* Stop calling "super" twice in Rails::Server#appCarlos Antonio da Silva2013-03-121-1/+4
| | | | Cache the value of "super" in a variable and use it instead.
* Add ENV['RACK_ENV'] support to rake runner/console/server.kennyj2012-12-061-1/+1
|
* copy the log level from the config settingsAaron Patterson2012-11-091-0/+1
|
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-141-7/+7
|
* add Rack::Lock for webrickAaron Patterson2012-08-211-0/+9
|
* Remove support for rails server RAILS_ENV=env-nameSam Oliver2012-05-301-5/+0
|
* use File.join rather than depend on PathnameAaron Patterson2012-05-231-1/+1
|
* and one more timeAditya Sanghi2012-04-241-1/+1
|
* stamp out ruby-debug19 with extreme prejudice :)Aditya Sanghi2012-04-171-1/+1
|
* fix rails server support of RAILS_ENV variableschneems2012-03-201-0/+5
| | | | | | | When launching rails server from the command line with a rails environment specified such as `rails server RAILS_ENV=production` an error would occur since rails will try to use `RAILS_ENV=production` as it's server. When launching rails with a specified server such as thin `rails server thin RAILS_ENV=production` no error will be thrown, but rails will not start up in the specified environment. This fixes both of those cases
* allow people to specify custom formatters, use the default formatter in ↵Aaron Patterson2012-03-121-0/+2
| | | | production so that PID and timestamp are logged. fixes #5388
* broadcasting to the console and remove file tailing middlewareAaron Patterson2012-01-201-1/+7
|
* do not do reverse lookups on incoming requests for webrick. fixes #4542Aaron Patterson2012-01-191-0/+1
|
* Use toplevel Rack::ContentLengthJeremy Kemper2011-10-191-1/+1
|
* Use again Rack's ContentLength middleware part 2Santiago Pastorino2011-10-181-0/+1
|
* Use again Rack's ContentLength middlewareSantiago Pastorino2011-10-181-1/+0
|
* Fixing Rails::Server#app under Rack::URLMapGuillermo Iguaran2011-06-071-1/+1
|
* Move content length to the server, this brings the same behavior as in rack 1.2.José Valim2011-05-231-0/+1
|
* Take into account the Rack::Server :SSLEnable option when building the ↵Daniel Martin2011-05-061-1/+2
| | | | application's URL
* reduce two method calls per request, 1 to method_missing and one to sendAaron Patterson2011-02-281-0/+4
|
* Allow a PID file to be specified to rails server [#5031 state:resolved]Sudara2010-07-081-0/+3
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Note that 'rails server' allows specifying mongrel, thin, etc [#4845 ↵Trevor Turk2010-06-221-1/+1
| | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Added absolute path for config.ru as well. Turns out this is also needed to ↵Ryan Duryea2010-06-201-1/+2
| | | | | | | | fix the daemon issue under ruby 1.8.7 [#4531 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Pass rack the absolute path of server's pid fileRyan Duryea2010-06-201-1/+1
| | | | | | | | | When running as a daemon, rack will cd to "/" and paths relative to the root of the rails app aren't valid when rack is setting up. Because of this, "rails server -d" was failing silently when trying to write it's pid file Signed-off-by: José Valim <jose.valim@gmail.com>
* Create tmp directories if required before starting server [#3907 state:resolved]Ravinder Singh2010-03-311-0/+5
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Fix server environment [#3877 status:resolved]Simo Niemelä2010-02-101-4/+11
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Add default values to output of 'rails server -h', hardcoded as Rack::Server ↵Prem Sichanugrist2010-02-101-3/+3
| | | | | | did since options doesn't have any data at the time of parsing arguments [#3910 status:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Fix 'rails server -h' double help banner. Correct its usage line. [#3874 ↵Henrik N2010-02-061-1/+4
| | | | | | status:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Default to sync instrumentation.José Valim2010-01-211-10/+1
|
* Fix an issue where log was not being tailed in the first request.José Valim2010-01-151-1/+14
|
* LogTailer should be invoked after all logs in threads were flushed.José Valim2010-01-151-5/+1
|
* Get everyone running on Rails.env and fix the broken environment settings ↵David Heinemeier Hansson2010-01-111-4/+3
| | | | for script/console and script/dbconsole
* script/server should init Rails by loading config.ruJoshua Peek2009-12-261-16/+4
| | | | Fixes "Rails 3.0 doesn't fucking work"
* Shift more responsibility from application class to its singleton instance. ↵Jeremy Kemper2009-12-231-5/+5
| | | | Treat instantiation and boot as separate steps. Use app.config rather than app.configuration.
* Fix an ivar name conflict in Rails::ServerCarlhuda2009-12-021-5/+5
|