aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/generators/app_base.rb
Commit message (Collapse)AuthorAgeFilesLines
* Rails::Generators::AppBase::GemfileEntry needs anonymous superclassAkira Matsuda2017-01-131-1/+1
| | | | | | it has some methods that override the accessors and calls the original accessors via `super` this partially reverts 9360b6be63b7a452535699bcf6ae853df7f5eea7
* class Foo < Struct.new(:x) creates an extra unneeded anonymous classAkira Matsuda2017-01-131-1/+1
| | | | because Struct.new returns a Class, we just can give it a name and use it directly without inheriting from it
* remove `skip_bundle` option from plugin generatoryuuji.yaginuma2016-12-311-3/+0
| | | | | | | Because `bundle install` is not executed regardless of whether the option is specified or not. Ref: fbd1e98cf983572ca9884f17f933ffe92833632a
* Remove deprecated support to passing a column to #quoteRafael Mendonça França2016-12-291-0/+1
|
* Privatize unneededly protected methods in RailtiesAkira Matsuda2016-12-251-15/+15
|
* Don't assign a default to `webpack`.Kasper Timm Hansen2016-12-121-2/+2
| | | | | | | Unintentionally makes `--webpack` implied on `rails new apper`. If passed `--webpack` Thor assigns `"webpack"` to `options[:webpack]`, so we can check for that instead of `"base"`.
* Add option to trigger JS framework-specific installation as part of webpack ↵David Heinemeier Hansson2016-12-121-2/+5
| | | | setup
* run `webpack` command only when webpack option is specifiedyuuji.yaginuma2016-12-101-1/+1
|
* gemfile entry method need to return an empty array rather than nil (#27318)Yuji Yaginuma2016-12-091-4/+4
| | | | | | | | | This fixes the following error when executing rails new command. ``` (erb):9:in `block in template': undefined method `comment' for nil:NilClass (NoMethodError) ``` Follow up to #27288
* Use GitHub webpacker until closer to releaseDavid Heinemeier Hansson2016-12-091-1/+1
|
* Basic --webpack delegation to new webpacker gem (#27288)David Heinemeier Hansson2016-12-091-0/+15
|
* Make Yarn the default, drop default vendor/asset directories (#27300)David Heinemeier Hansson2016-12-081-51/+2
|
* Yarn: Move node_modules, package.json, and yarn.lock file to vendor (#27245)David Heinemeier Hansson2016-12-011-1/+1
| | | Move node_modules, package.json, and yarn.lock file to vendor
* use `Gem.win_platform?` to check windows Ruby platformsyuuji.yaginuma2016-11-301-1/+1
| | | | | `Gem.win_platform?` check if it is Windows more accurately. Ref: https://github.com/ruby/ruby/blob/ruby_2_2/lib/rubygems.rb#L945..L952
* Merge pull request #26836 from Liceth/npmGuillermo Iguaran2016-11-291-0/+52
|\ | | | | Add Yarn support in new apps using --yarn option
| * Add package.json for Yarn if --yarn option is addedLiceth Ovalles2016-11-281-0/+52
| |
* | rails-ujs is now shipped with Action ViewGuillermo Iguaran2016-11-291-3/+0
|/
* Don't add jQuery by default in new apps and use rails-ujs as UJS adapter insteadGuillermo Iguaran2016-11-211-3/+8
|
* Merge pull request #25248 from bluesh55:features/skip-coffeeSean Griffin2016-11-121-1/+6
|\ | | | | | | Add --skip-coffee generating option
| * Add --skip-coffee generating optionseunghwan oh2016-06-021-1/+6
| | | | | | | | | | | | Usage `rails new awesome-project --skip-coffee`
* | Do not point to the 5-0-stable branchRafael Mendonça França2016-09-131-1/+1
| | | | | | | | Master based applications should be pointing to master
* | Fix Remaining Case-In-Assignment Statement FormattingAlex Kitchens2016-09-061-7/+8
| | | | | | | | | | | | | | | | | | Recently, the Rails team made an effort to keep the source code consistent, using Ruboco (bb1ecdcc677bf6e68e0252505509c089619b5b90 and below). Some of the case statements were missed. This changes the case statements' formatting and is consistent with changes in 810dff7c9fa9b2a38eb1560ce0378d760529ee6b and db63406cb007ab3756d2a96d2e0b5d4e777f8231.
* | applies remaining conventions across the projectXavier Noria2016-08-061-5/+5
| |
* | applies new string literal convention in railties/libXavier Noria2016-08-061-60/+60
| | | | | | | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* | Show supported DBs first in `rails new --help`Akira Matsuda2016-08-031-5/+5
| |
* | A generated app should not include Uglifier with `--skip-javascript` option.Ben Pickles2016-07-261-3/+5
| |
* | Do not run `bundle install` when generating a new plugin.Rafael Mendonça França2016-07-011-1/+1
| | | | | | | | | | | | Since bundler 1.12.0, the gemspec is validated so the `bundle install` command will fail just after the gem is created causing confusion to the users. This change was a bug fix to correctly validate gemspecs.
* | Merge pull request #25607 from sstephenson/turbolinks-5-finalRafael Mendonça França2016-06-301-1/+1
|\ \ | | | | | | | | | Update to Turbolinks 5.0.0 final
| * | Update to Turbolinks 5.0.0 finalSam Stephenson2016-06-301-1/+1
| |/
* / Point to released coffee-railsRafael Mendonça França2016-06-301-1/+1
|/
* Bump jbuilder dependency to version 2.5.0 for compatibility fixesDavid Heinemeier Hansson2016-05-311-1/+1
|
* Use sass-rails and coffee-rails that work with Rails 5.1Rafael Mendonça França2016-05-101-2/+2
|
* revises fileutils dependencies in railtiesXavier Noria2016-04-111-0/+1
| | | | | | With the exception of what is loaded in active_support/rails, each file is responsible for its own dependencies. You cannot rely on runtime order of execution.
* [close #23681] Use puma 3.0.0+ schneems2016-02-261-1/+1
| | | | | Puma 3.0 and up introduced compatibility to read from `config/puma.rb` when booting from the command `$ rails server`https://github.com/puma/puma/pull/856.
* Always use the released coffee-rails in new applicationsRafael Mendonça França2016-02-241-6/+1
| | | | | coffee-rails is stable now so we don't need to point to the master branch.
* Use the trick to get beta releases in the GemfileRafael Mendonça França2016-02-231-1/+1
|
* New apps get the Turbolinks beta gemSam Stephenson2016-02-231-2/+2
|
* adds --skip-listen to the application generator [closes #23590]Xavier Noria2016-02-171-0/+7
|
* enables the evented monitor in new applicationsXavier Noria2016-02-101-0/+4
|
* - app generate option --skip-sprockets leaves jquery-rails gem, which relies ↵Vipul A M2016-02-041-1/+1
| | | | | | | | on sprockets environment - Remove jquery-rails if --skip-sprockets is true Fixes #23431
* Turbolinks has moved outDavid Heinemeier Hansson2016-02-041-1/+1
| | | | All grown up and shit!
* Redis is now only needed if you want to use Action Cable in productionDavid Heinemeier Hansson2016-02-041-2/+2
| | | | So no need to have it on by default in the Gemfile.
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 22:37:56 +0000