- 10 2月, 2016 2 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
- 04 2月, 2016 2 次提交
-
-
由 Vipul A M 提交于
- app generate option --skip-sprockets leaves jquery-rails gem, which relies on sprockets environment - Remove jquery-rails if --skip-sprockets is true Fixes #23431
-
由 Prem Sichanugrist 提交于
Redis now included in Gemfile but commented out. This change was made in 91864439 and is causing the test failure. See https://travis-ci.org/rails/rails/jobs/106994913#L1025
-
- 02 2月, 2016 1 次提交
-
-
由 yuuji.yaginuma 提交于
Test of Rails API should be in `api_app_generator_test.rb`.
-
- 31 1月, 2016 1 次提交
-
-
由 Matthew Draper 提交于
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.
-
- 30 1月, 2016 1 次提交
-
-
由 schneems 提交于
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
-
- 29 1月, 2016 1 次提交
-
-
由 Ryan Manuel 提交于
-
- 23 1月, 2016 1 次提交
-
-
由 Dave Riddle 提交于
-
- 22 1月, 2016 2 次提交
-
-
由 Jon Moss 提交于
-
由 JuanitoFatas 提交于
-
- 19 1月, 2016 2 次提交
- 31 12月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
It was removed by mistake at 877a411d
-
- 22 12月, 2015 2 次提交
-
-
由 yuuji.yaginuma 提交于
`rack-cors` gem is defined in Gemfile by default only if the api, not defined by default in rails app.
-
由 Jey Balachandran 提交于
The Action Cable generators creates four files which need to be removed if `skip_action_cable` is set. 1. `app/assets/javascripts/cable.coffee` 2. `app/channels/application_cable/channel.rb` 3. `app/channels/application_cable/connection.rb` 4. `config/redis/cable.yml` Fixes #22669.
-
- 18 12月, 2015 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 17 12月, 2015 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 16 12月, 2015 1 次提交
-
-
由 Genadi Samokovarov 提交于
It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present.
-
- 15 12月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 14 12月, 2015 1 次提交
-
-
由 Genadi Samokovarov 提交于
Web Console 3.0.0 is compatible with Rails 5, while the 2.x.x releases aren't.
-
- 30 10月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
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.
-
- 24 9月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 18 6月, 2015 2 次提交
-
-
由 Diego Carrion 提交于
fixes #20042
-
由 Mehmet Emin İNAÇ 提交于
-
- 30 5月, 2015 1 次提交
-
-
由 Yoong Kang Lim 提交于
A lot of scripts assumes the existence of this folder and most would fail if it is absent. One example of this is `rake restart` (before the previous commit) – it tries to `touch tmp/restart.txt`, which would fail if `tmp` does not exist, which was the case for a freshly-cloned project as `tmp` is `.gitignored` by default. See #20299. [Yoong Kang Lim, Sunny Juneja]
-
- 20 4月, 2015 1 次提交
-
-
由 Godfrey Chan 提交于
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.
-
- 24 3月, 2015 1 次提交
-
-
由 Jeroen van Baarsen 提交于
* Jobs generated now inherent from ApplicationJob * ApplicationJob inherents from ActiveJob::Base * Added entry to changelog Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 19 3月, 2015 1 次提交
-
-
由 Arthur Neves 提交于
-
- 22 2月, 2015 1 次提交
-
-
由 Josef Šimánek 提交于
Deprecate `required` option in favor of `optional` for belongs_to.
-
- 07 2月, 2015 2 次提交
-
-
由 Xavier Noria 提交于
README.rdoc was generated to support the doc:app task. Now that this task is gone we can switch to Markdown, which is nowadays a better default.
-
由 Xavier Noria 提交于
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.
-
- 28 1月, 2015 2 次提交
-
-
由 Yves Senn 提交于
It's a thin layer to provide easy access to sample files throughout test-cases. This adds the directory `test/fixtures/files` to newly generated applications.
-
由 Melanie Gilman 提交于
Rails no longer generates Test::Unit files by default.
-
- 14 1月, 2015 1 次提交
-
-
由 Sean Griffin 提交于
Fixes #18473
-
- 05 1月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
bebugger doesn't work with Ruby 2.2 so we don't need to support it anymore
-
- 03 1月, 2015 1 次提交
-
-
由 claudiob 提交于
This stems from [a comment](rails#17227 (comment)) by @dhh. In summary: * New Rails 5.0 apps will not accept `return false` as a way to halt callback chains, and will not display a deprecation warning. * Existing apps ported to Rails 5.0 will still accept `return false` as a way to halt callback chains, albeit with a deprecation warning. For this purpose, this commit introduces a Rails configuration option: ```ruby config.active_support.halt_callback_chains_on_return_false ``` For new Rails 5.0 apps, this option will be set to `false` by a new initializer `config/initializers/callback_terminator.rb`: ```ruby Rails.application.config.active_support.halt_callback_chains_on_return_false = false ``` For existing apps ported to Rails 5.0, the initializers above will not exist. Even running `rake rails:update` will not create this initializer. Since the default value of `halt_callback_chains_on_return_false` is set to `true`, these apps will still accept `return true` as a way to halt callback chains, displaying a deprecation warning. Developers will be able to switch to the new behavior (and stop the warning) by manually adding the line above to their `config/application.rb`. A gist with the suggested release notes to add to Rails 5.0 after this commit is available at https://gist.github.com/claudiob/614c59409fb7d11f2931
-
- 02 1月, 2015 1 次提交
-
-
由 claudiob 提交于
-
- 23 12月, 2014 2 次提交
-
-
由 Sean Griffin 提交于
The changes in #18149 added tests for the app generator, but only fixed it for the plugin generator (I should have let CI finish though I think it would have failed as an allowed failure).
-
由 Arthur Neves 提交于
-