aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/generators/app_base.rb
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #23057 from schneems/schneems/default-puma-configRichard Schneeman2016-02-011-0/+10
|\ | | | | Add Default Puma Config
| * Add Default Puma Configschneems2016-01-291-0/+10
| | | | | | | | | | | | | | | | | | | | | | When the `puma` command is run without any configuration options it will detect presence of a `config/puma.rb` file and use that. Currently there is discrepancy between `puma` command and `rails server` but Evan said it would be reasonable to add in reading in config from the default location. I am working on that right now as a feature in puma/puma. Why do we need this? By default Puma uses 16 threads, and by default ActiveRecord only has 5 threads. Due to the architecture of AR it is guaranteed that if you're running with fewer DB connections than your server has threads you will hit `ActiveRecord::ConnectionTimeoutError ` eventually if your app gets modest amounts of traffic. Since we are providing a default webserver, we should provide reasonable configuration for that webserver. This PR does a few things, first it sets the default Puma thread count to 5 to mach ActiveRecord's default. It sets the default environment to `"development"` and the default port to 300 so that booting the server with `$ puma` will give you the same default port as `rails server`. It is worth mentioning that by reading in from `PORT` environment variable this config can work with containerized deployments, such as on Heroku. We are not using worker processes by default, that way JRuby and windows devs can use this configuration without modification. I went ahead and included a default `on_worker_boot`. It won't be used unless a worker count is specified, that means this config will not use it. Even though it's not being used now It will make someone who wants to try modifying their config to run extra workers easier. cc/ @pixeltrix
* | Switch the default redis adapter to a single-stream modelMatthew Draper2016-02-011-1/+0
|/ | | | | | This new adapter does get a little more intimate with the redis-rb gem's implementation than I would like, but it's the least bad of the approaches I've come up with.
* Add em-hiredis and redis as default Gems for new applicationsJon Moss2016-01-181-0/+10
|
* Add sass-rails back to the default GemfileRafael Mendonça França2015-12-301-0/+2
| | | | It was removed by mistake at 877a411d0c16baa4e670dae9a28f5cfcc201adc1
* Changed default value of `:rc` option to `nil`Prathamesh Sonpatki2015-12-251-1/+1
| | | | | | | - This fixes an error thrown by Thor because type of default value of `:rc` option which is `:boolean` does not match with it's default type which is `string`. - Ref - https://github.com/erikhuda/thor/blob/master/lib/thor/parser/option.rb#L125
* Merge pull request #22657 from matthewd/loosen-versionRafael Mendonça França2015-12-181-1/+15
|\ | | | | | | Allow normal version updates within a release series
| * Allow normal version updates within a release seriesMatthew Draper2015-12-181-1/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We originally chose to apply very strict versioning on the `rails` entry in the Gemfile, because our future versioning policy was not strongly defined. Now it is, and our policy is very much designed on the expectation that people will regularly update to the latest patch level in their release series... so we should encourage that. Of course, Gemfile.lock will do its job and prevent unplanned updates, just as it does for every other gem in the bundle... but if you run `bundle update`, we want to get you the latest bug/security fixes without requiring a manual edit of the Gemfile entry. Our current version could be a few different shapes, so it takes a bit of work to find the right specifier, but in principle, we match anything of the form x.y.*, where x.y matches our current release series.
* | More sensible ordering with the more important options firstDavid Heinemeier Hansson2015-12-181-12/+12
| |
* | List the major frameworks you can remove togetherDavid Heinemeier Hansson2015-12-181-3/+3
| |
* | Use released rackRafael Mendonça França2015-12-181-2/+1
|/
* Use release sprockets-railsRafael Mendonça França2015-12-171-1/+0
|
* Use released arelRafael Mendonça França2015-12-171-1/+0
|
* Merge branch 'master' into merge-action-cableRafael Mendonça França2015-12-161-5/+1
|\
| * Use sprockets 3 in the Rails 5 releaseRafael Mendonça França2015-12-161-2/+0
| |
| * Do not default to any SerializerSantiago Pastorino2015-12-151-3/+1
| | | | | | | | We will wait until 5.1 to make a decision
* | Add option to skip Action CableRafael Mendonça França2015-12-141-1/+4
|/
* Add version constraint to database gem in generated applicationRafael Mendonça França2015-10-291-11/+22
| | | | | | We are using the same version constraint in the database adapters so when a new version of the adapter that doesn't work with the version of rails is released we don't break new applications.
* dev and edge have some common, so factor it out.Eric Guo2015-09-131-10/+7
|
* smooth move aaron.... :bomb:Aaron Patterson2015-08-201-2/+2
|
* point at rack masterAaron Patterson2015-08-201-0/+2
|
* Migrate to Sprockets 4.Andrei Istratii2015-08-191-2/+4
|
* Disable jbuilder for Rails API apps, meanwhile it doesn't play nicelySantiago Pastorino2015-06-111-0/+2
|
* api option implies skipping javascript & sprocketsSantiago Pastorino2015-06-111-2/+2
|
* rails new --api generates an api app skeletonSantiago Pastorino2015-06-111-2/+2
|
* Use sprockets-rails from github repoYoong Kang Lim2015-06-021-0/+2
| | | | See #20397
* Omit .keep in .gitignore when generated with --skip-keeps.Ben Pickles2015-05-221-1/+5
|
* Implicitly skip spring for `rails new --dev`Godfrey Chan2015-04-201-1/+1
| | | | | | Spring seems like an obvious foot gun for the `--dev` setup, presumably you are about to make lots of changes to the codebase, so it should always reload the framework.
* Print `bundle install` output in `rails new` as soon as it's availableMax Holder2015-03-281-6/+6
| | | | | | | | | | | | | | | Previously, running `rails new` would not print any of the output from `bundle install` until all the gems had finished installing. This made it look like the generator was hanging at the `bundle install` step. This commit switches to using `system` so that the bundle command can output as it needs to. This has the added benefit of including output bundler produces on standard error, which the previous code ignored since backticks only capture standard out. This is not a big deal right now since bundler does not currently print errors to standard error, but that may change in the future (see: bundler/bundler/issues/3353).
* Update sprockets links to point to rails orgJoshua Peek2015-03-131-1/+1
|
* Remove documentation tasksXavier Noria2015-02-061-6/+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.
* Use public Module#include, in favor of https://bugs.ruby-lang.org/issues/8846robertomiranda2015-01-311-1/+1
| | | | ref: https://github.com/rails/rails/pull/18763#issuecomment-72349769
* Change option description and update test namesMelanie Gilman2015-01-291-1/+1
|
* Update option to skip test in generatorsMelanie Gilman2015-01-271-3/+3
| | | | Rails no longer generates Test::Unit files by default.
* Add --skip-action-mailer (or -M) to rails generateclaudiob2015-01-011-1/+5
|
* Fix Duplicate web-console entries in GemfileNorimasaAndo2014-12-141-10/+0
|
* New applications should use sass-rails 5.0Rafael Mendonça França2014-12-121-6/+1
|
* Rails master requires arel masterRafael Mendonça França2014-12-121-2/+8
|
* Align the GemfileEntry API with stable branchesGodfrey Chan2014-12-121-5/+9
| | | | See 63462ec
* Use latest web-console when using --dev or --edgeSam Ruby2014-12-051-0/+10
| | | | | | Fixes: http://intertwingly.net/projects/AWDwR4/checkdepot-215/makedepot.log
* We don't need to use sass-rails 5.0.0.betaRafael Mendonça França2014-11-281-2/+1
|
* Revert "Test against rack master"Santiago Pastorino2014-11-271-2/+2
| | | | This reverts commit 2a4e14db981e38611667d407a975600ee720ada7.
* Test against rack masterRafael Mendonça França2014-11-261-2/+2
|
* Use jquery-rails 4.0.0Rafael Mendonça França2014-11-251-8/+2
|
* Fix syntax error :bomb:Rafael Mendonça França2014-11-251-2/+2
|
* Use released rails-dom-testingRafael Mendonça França2014-11-251-2/+0
|
* Fix sprockets-rails dependency danceArthur Neves2014-11-241-2/+0
| | | | | | - Remove sprockets-rails from generated Gemfile as rails has a hard-dependency on it - Also allow sprockets-rails >= 2.0.0
* Generate new applications with the right rails-dom-testing versionRafael Mendonça França2014-11-171-2/+4
|
* Skip spring install in Cygwin due to fork() bad support.michaeljayt2014-11-171-1/+1
| | | | See also: https://www.cygwin.com/faq.html#faq.using.fixing-fork-failures
* Add back --skip-turbolinks and remove --skip-gemsRafael Mendonça França2014-10-261-6/+9
| | | | | | | For the most part of cases --skip-gems option just remove one line in the Gemfile. This is not worth for the complexity it adds. Closes #17196
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 07:37:25 +0000