aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/command_line.md
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #33229 from ↵Matthew Draper2018-07-251-87/+82
|\ | | | | | | | | albertoalmagro/albertoalmagro/prefer-rails-command-over-bin-rails Prefer rails command over bin/rails
| * Homogenize rails commands and former rake tasksAlberto Almagro2018-07-061-58/+53
| | | | | | | | | | | | | | | | | | | | | | | | This commit integrates most used previously rake commands into the above outer list. Ordering is based on their individual predicted frequency of use. Separation between bin/rails tasks is also removed to display all commands at the same level. It also removes references to rake and tasks and substitutes them for command.
| * Recommend use of rails over bin/railsAlberto Almagro2018-07-061-38/+38
| | | | | | | | | | | | | | | | | | As discussed in #33203 rails command already looks for, and runs, bin/rails if it is present. We were mixing recommendations within guides and USAGE guidelines, in some files we recommended using rails, in others bin/rails and in some cases we even had both options mixed together.
* | Rails guides are now served over httpsPaul McMahon2018-07-241-3/+3
|/ | | | | http links will be redirected to the https version, but still better to just directly link to the https version.
* Merge pull request #33220 from anniecodes/notes-commandKasper Timm Hansen2018-07-051-28/+53
|\ | | | | Adds `Rails::Command::NotesCommand` and makes `rake notes` use it under the hood
| * [ci skip] Update documentation related to `rails notes`Annie-Claude Côté2018-07-031-28/+53
| | | | | | | | | | | | * Get rid of references to rake notes in the documentation * Get rid of references to environement variables used in SourceAnnotationExtractor * Updates the command line guide to reflect the new rails notes API
* | OS X -> macOS [Closes #30313]Xavier Noria2018-06-231-2/+2
|/ | | | [Jon Moss & Xavier Noria]
* Added a lot of Oxford commasAnthony Crumley2018-05-101-7/+7
| | | | | | | [ci skip] A regular expression was used to find a lot of missing Oxford commas and add them. The regular expression was as follows. ", ([a-zA-Z0-9.\`:'\"]+ ){1,6}(or|and) "
* Rails 6 requires Ruby 2.4.1+Jeremy Daer2018-02-171-4/+4
| | | | | | Skipping over 2.4.0 to sidestep the `"symbol_from_string".to_sym.dup` bug. References #32028
* Rails 6 requires Ruby 2.3+Jeremy Daer2018-02-171-1/+1
|
* Use `-e` option to specify the environment in console command [ci skip]yuuji.yaginuma2017-11-101-1/+1
| | | | | Passing the environment's name as a regular argument is deprecated in 48b249927375465a7102acc71c2dfb8d49af8309.
* Cosmetic fixes [ci skip]Yauheni Dakuka2017-10-061-1/+1
|
* Update database config in The Rails Comamnd Line of guide [ci skip]Yoshiyuki Hirano2017-08-201-4/+7
|
* Fix guide about command_line [ci skip]Yoshiyuki Hirano2017-08-151-0/+3
|
* Clear screenshots files in `tmp:clear` taskyuuji.yaginuma2017-06-271-7/+8
| | | | | | | | | If system test fails, it creates screenshot under `tmp/screenshots`. https://github.com/rails/rails/blob/34fe2a4fc778d18b7fe6bdf3629c1481bee789b9/actionpack/lib/action_dispatch/system_testing/test_helpers/screenshot_helper.rb#L45 But currently, screenshot files is not cleared by `tmp:clear` task. This patch make clears screenshot files with `tmp:clear` task as well as other tmp files.
* Update middleware listJon Moss2017-03-251-1/+1
| | | | | | Taken from `bin/rails about` run on a v5.1.0.rc1 application. [ci skip]
* Upgrade various Rails 5.0 references to 5.1Jon Moss2017-03-251-4/+4
| | | | | | | RC1 is out, `5-1-stable` has been created, figured it was time to start updating this stuff :) [ci skip]
* Update schema cache doc in guides/command_lineKir Shatrov2016-12-311-2/+2
|
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2016-08-021-1/+7
|\
| * Add note about `config.annotations.register_directories` option in the ↵Prathamesh Sonpatki2016-07-101-1/+7
| | | | | | | | | | | | guides [ci skip] - Followup of #25692.
* | Correct link for model generator field typesJosh Justice2016-07-131-1/+1
|/ | | | | | The most complete list of field types appears in the `SchemaStatements` docs rather than the `TableDefinition` docs. The change to link to `SchemaStatements` means that the explanation for the `index` parameter is no longer available on the linked-to page. A brief explanation of the `index` parameter is added directly in the guide to make up for this.
* The `ActiveRecord::ConnectionAdapters::ConnectionManagement` and ↵Vipul A M2016-05-161-1/+1
| | | | | | | `ActiveRecord::QueryCache` middlewares were removed with `Executor` addition on d3c9d808e3e242155a44fd2a89ef272cfade8fe8 Removes traces and reference of these from all places. [ci skip]
* Replace ActionDispatch::LoadInterlock with ActionDispatch::Executor in ↵willnet2016-04-301-1/+1
| | | | | | | guides [ci skip] Guides should be updated because ActionDispatch::LoadInterlock was replaced with ActionDispatch::Executor at #23807.
* MariaDB Documentationiangilfillan2016-04-141-1/+1
|
* Match Puma 3 startup messages [ci skip]Sam Ruby2016-03-041-3/+4
|
* SQLite 2 support has been dropped [ci skip]Ryuta Kamizono2016-02-041-1/+1
|
* update supported version of PostgreSQL in docs [ci skip]yuuji.yaginuma2016-02-031-1/+1
| | | | Follow up to #23434
* Merge pull request #22857 from bdewater/interlock-docVipul A M2016-02-011-1/+1
|\ | | | | Update middleware docs regarding ActionDispatch::LoadInterlock [ci skip]
| * Update middleware docs regarding ActionDispatch::LoadInterlock [ci skip]Bart de Water2016-01-311-1/+1
| |
* | Rails 5.0+ rake commands implemented in Rails Framework itself. We prefer to ↵Gaurav Sharma2016-01-221-43/+62
| | | | | | | | use bin/rails instead of rake [ci skip]
* | Merge pull request #23125 from Gaurav2728/update_puma_as_webserverRafael França2016-01-191-7/+8
|\ \ | | | | | | [ci skip] update guide for Puma web server instead of Webrick
| * | [ci skip] update guide for Puma web server instead of WebrickGaurav Sharma2016-01-201-7/+8
| | | | | | | | | Rails 5.0 default server puma web server. following commit - https://github.com/rails/rails/commit/ae48ea69
* | | - Changed from bin/rake to bin/rails at more application places.Vipul A M2016-01-201-1/+1
|/ / | | | | | | | | | | | | - Only ones left are from the upgrading guide, and command line guide explicit section about rake Follow up of https://github.com/rails/rails/pull/23119 [ci skip]
* / rake log:clear task updated refs[#22544]Pramod2016-01-091-1/+1
|/ | | | | | | | - Avoided truncating all files if no ENV['LOGS'] specified - Updated task to accept LOGS=all for truncating all files from log/ i.e. log/*log - If no LOGS specified will truncates standard environment log files i.e. 'development,test,production' - CHANGELOG & guide update added - bin/setup test cases fixed
* [ci skip] `rails new project` generates README.md nowAkshay Vishnoi2015-12-211-3/+3
|
* Revert "removing Rack::Runtime from the default stack."Aaron Patterson2015-10-031-1/+1
| | | | | | | | | | | | | | | | | | This reverts commit 37423e4ff883ad5584bab983aceb4b2b759a1fd8. Jeremy is right that we shouldn't remove this. The fact is that many engines are depending on this middleware to be in the default stack. This ties our hands and forces us to keep the middleware in the stack so that engines will work. To be extremely clear, I think this is another smell of "the rack stack" that we have in place. When manipulating middleware, we should have meaningful names for places in the req / res lifecycle **not** have engines depend on a particular constant be in a particular place in the stack. This is a weakness of the API that we have to figure out a way to address before removing the constant. As far as timing attacks are concerned, we can reduce the granularity such that it isn't useful information for hackers, but is still useful for developers.
* removing Rack::Runtime from the default stack.Aaron Patterson2015-10-021-1/+1
| | | | | | | | | | | | The runtime header is a potential target for timing attacks since it returns the amount of time spent on the server (eliminating network speed). Total time is also not accurate for streaming responses. The middleware can be added back via: ```ruby config.middleware.ues ::Rack::Runtime ```
* mostly remove the ParamsParser middlewareAaron Patterson2015-09-181-1/+1
| | | | | This can still be added to the middleware stack, but is really not necessary. I'll follow up with a commit that deprecates the constant
* [ci skip] Add link to testing guideBrooks Reese2015-08-101-1/+7
|
* update Rails Command Line guide pageGaurav Sharma2015-06-091-2/+2
|
* [ci skip] Fix linked html fileyui-knk2015-04-211-1/+1
|
* Merge pull request #19753 from jonatack/use-ruby-2-2-2Guillermo Iguaran2015-04-131-2/+2
|\ | | | | Upgrade to Ruby 2.2.2
| * Upgrade to Ruby 2.2.2Jon Atack2015-04-141-2/+2
| | | | | | | | and fix the grammar in the ruby_version_check.rb user message.
* | correct the directory which rake notes look by default [ci skip]yuuji.yaginuma2015-04-061-1/+1
|/
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2015-03-261-1/+1
|\ | | | | | | | | Conflicts: guides/source/4_0_release_notes.md
| * Rails 5 requires 2.2.1. [ci skip]Juanito Fatas2015-03-241-1/+1
| | | | | | | | Follow up of https://github.com/rails/rails/pull/19263.
* | Adds an example of how to access the arguments passed to a custom rake task ↵Mohnish G J2015-03-161-2/+2
|/ | | | [ci skip]
* Section explaining how rails runner accepts code in a ruby file.Waseem Ahmad2015-02-261-0/+6
| | | | [ci skip]
* Remove documentation tasksXavier Noria2015-02-061-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch removes the tasks doc:app, doc:rails, and doc:guides. In our experience applications do not generate APIs using doc:app. Methods may be certainly documented for maintainers, annotated with YARD tags, etc. but that is intended to be read with the source code, not in a separate website. Then, teams also have typically selected topics written down in Markdown files, or in a GitHub wiki... that kind of thing. If a team absolutely needs to generate application documentation for internal purposes, they can still easily write their own task. Regarding doc:rails and doc:guides, we live in 2015. We are used to go to online docs all the time. If you really want access to the API offline RubyGems generates it for every Rails component unless you tell it not to, and you can checkout the Rails source code to read the guides as Markdown, or download them for a Kindle reader. All in all, maintaining this code does not seem to be worthwhile anymore. As a consequence of this, guides (+3 MB uncompressed) won't be distributed with the rails gem anymore. Of course, guides and API are going to be still part of releases, since documentation is maintained alongside code and tests. Also, time permitting, this will allow us to experiment with novel ways to generate documentation in the Rails docs server, since right now we were constrained by being able to generate them in the user's environment.
* - Changed `IN` to `ON` in markdown renderer conditionVipul A M2015-01-141-1/+1
| | | | - Changed `IN` to `ON` in all note sentences in guides.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 10:30:12 +0000