aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/generators
Commit message (Collapse)AuthorAgeFilesLines
* clarification to prevent confusing newbies; Passenger/Unicorn are app ↵Michael de Silva2012-03-281-1/+1
| | | | servers, Apache/Nginx are the web servers along with thin a la Heroku etc.
* Changed the config.assets.manifest to nil in the comments in the production ↵Anuj Dutta2012-03-281-1/+1
| | | | config template.
* Adding comma to correct syntax in comment.Jesse Brown2012-03-191-1/+1
|
* Rubyracer does not work on ruby, so add it to Gemfile with :ruby platform onlyPiotr Sarnacki2012-03-171-1/+1
|
* Remove --http.José Valim2012-03-148-137/+6
|
* Fix scaffold controller template, ensure rake scaffold test pass by defaultCarlos Antonio da Silva2012-03-141-2/+2
|
* Do not generate app/views and sprockets entries on http appCarlos Antonio da Silva2012-03-141-0/+5
| | | | [Carlos Antonio da Silva & Santiago Pastorino]
* Generate special controller and functional test templates for http appsCarlos Antonio da Silva2012-03-145-3/+126
| | | | | | | | | | | | The main goal is to not generate the format.html block in scaffold controller, and to generate a different functional test as we don't rely on redirects anymore, we should test for http responses. In addition to that, the :edit action is removed from the http controller and the edit route is not generated by default, as they usually do not make sense in this scenario. [Carlos Antonio da Silva & Santiago Pastorino]
* Rename http-only app generator option to httpCarlos Antonio da Silva2012-03-143-5/+5
| | | | [Carlos Antonio da Silva & Santiago Pastorino]
* Move http only option to AppGeneratorCarlos Antonio da Silva2012-03-142-3/+3
| | | | [Carlos Antonio da Silva & Santiago Pastorino]
* Generate middleware http_only! config when running http only app generatorCarlos Antonio da Silva2012-03-141-1/+10
| | | | [Carlos Antonio da Silva & Santiago Pastorino]
* Add http-only option to Rails app generatorCarlos Antonio da Silva2012-03-143-5/+8
| | | | | | | Change application controller template accordingly, to inherit from ActionController::HTTP and not generate protect_from_forgery call. [Carlos Antonio da Silva & Santiago Pastorino]
* Add ActionController::HTTPSantiago Pastorino2012-03-141-1/+1
| | | | | | More info http://edgeguides.rubyonrails.org/api_app.html [Carlos Antonio da Silva & Santiago Pastorino]
* Remove key_value helper now that master is 1.9 only and we always useRafael Mendonça França2012-03-139-35/+21
| | | | the 1.9 hash syntax in the generators.
* Add sprockets-rails to generated Gemfile. This should be reverted after ↵Guillermo Iguaran2012-03-131-0/+2
| | | | sprockets-rails release on rubygems
* The sprockets railtie was moved to sprockets/rails/railtieGuillermo Iguaran2012-03-132-2/+2
|
* Merge pull request #5415 from rafaelfranca/refactorJosé Valim2012-03-131-1/+1
|\ | | | | Refactor the test_unit scaffold generator to use the key_value method
| * Refactor the test_unit scaffold generator to use the key_value methodRafael Mendonça França2012-03-131-1/+1
| |
* | Merge pull request #572 from sikachu/remove_activeresourceJosé Valim2012-03-132-2/+0
|\ \ | | | | | | Remove Active Resource source files from the repository.
| * | Remove Active Resource source files from the repositoryPrem Sichanugrist2012-03-132-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dear Active Resource, It's not that I hate you or anything, but you didn't get much attention lately. There're so many alternatives out there, and I think people have made their choice to use them than you. I think it's time for you to have a big rest, peacefully in this Git repository. I will miss you, @sikachu.
* | | Check for existence of exactly the called `fixture_path=` methodPiotr Sarnacki2012-03-131-2/+2
|/ /
* | Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-03-131-0/+2
|\ \ | |/ |/|
| * Advise to keep secret token privateFilipe Moreira2012-03-121-0/+2
| |
* | Merge pull request #5397 from rafaelfranca/fix-scaffoldJosé Valim2012-03-132-2/+23
|\ \ | | | | | | Do not use the attributes hash in the scaffold functional tests
| * | Use the attributes hash explicitlyRafael Mendonça França2012-03-132-6/+18
| | |
| * | Do not use the attributes hash in the scaffold functional testsRafael Mendonça França2012-03-122-2/+11
| | |
* | | Fixed problem when fixture_path is not always defined (incidentally, only ↵Philip Arndt2012-03-131-1/+3
| | | | | | | | | | | | when ActiveRecord is according to test_help.rb).
* | | Fixes issue #5193 using the instructions provided in the issue.Philip Arndt2012-03-131-0/+3
| | |
* | | allow people to specify custom formatters, use the default formatter in ↵Aaron Patterson2012-03-121-0/+3
|/ / | | | | | | production so that PID and timestamp are logged. fixes #5388
* | Merge pull request #5326 from lest/patch-2Michael Koziarski2012-03-101-1/+3
|\ \ | |/ |/| configure how unverified request will be handled
| * configure how unverified request will be handledSergey Nartimov2012-03-091-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | can be configured using `:with` option in `protect_from_forgery` method or `request_forgery_protection_method` config option possible values: - :reset_session (default) - :exception new applications are generated with: protect_from_forgery :with => :exception
* | Revert "let the connection pool of new applications have size 1 rather than 5"Xavier Noria2012-03-073-27/+9
|/ | | | | | | Reason: Temporarily reverting this because it has uncovered an issue that prevents Sam's test suite from passing. This reverts commit 9b2c38b7bd582d9712c3779294a9bccde7bbd548.
* Only add the whitelist_attributes option if ActiveRecord is presentRafael Mendonça França2012-03-041-1/+1
|
* Whitelist all attribute assignment by default.Michael Koziarski2012-03-051-1/+1
| | | | Change the default for newly generated applications to whitelist all attribute assignment. Also update the generated model classes so users are reminded of the importance of attr_accessible.
* ruby19: no need to rescue when requiring 'rdoc/task' in Ruby >= 1.9Akira Matsuda2012-02-271-7/+2
|
* let the connection pool of new applications have size 1 rather than 5Xavier Noria2012-02-263-9/+27
| | | | | | | | | The majority of Rails applications are multiprocess, people may wonder why rails new generates a default pool of 5, does my application need a connection pool of 5? By generating a default of 1 database.yml is much more clear, and with the comment people know what is the connection pool for, and they know it has to be bigger for multithread apps.
* consistently mention first patch, then putXavier Noria2012-02-242-5/+5
| | | | | | There was a mix, sometimes patch first, sometimes put first. Use always patch first, since this is going to be the primary verb for updates.
* uses PATCH for the forms of persisted records, and routes PATCH and PUT to ↵Xavier Noria2012-02-241-3/+0
| | | | the update action of resources
* removes the reconnect key from the database.yml generated for MySQLXavier Noria2012-02-241-12/+0
| | | | | | | | | | The reconnect flag does not play nicely with transactions and so it is of little use in Rails applications. Thus, albeit supported by mysql2, it does not deserve such a prominent place in the generated database.yml, which should be a representative config example. Note that the flag is false by default. Advanced users know from mysql2 docs that the flag is available.
* explains why reconnect is false by default in the database.yml generated for ↵Xavier Noria2012-02-241-1/+10
| | | | MySQL
* Use consistent whitespace for commented options.Felix Bünemann2012-02-231-1/+1
|
* Move config.autoflush_log to correct template.Felix Bünemann2012-02-232-3/+3
| | | | | | This accidentally ended up in the development template instead of the production template, where it makes most sense.
* Always default to flushing enabledFelix Bünemann2012-02-231-1/+1
|
* Advertise autoflush option in production templateFelix Bünemann2012-02-231-0/+3
|
* Add config.default_method_for_update to support PATCHDavid Lee2012-02-223-5/+8
| | | | | | | | | | | | | | | | PATCH is the correct HTML verb to map to the #update action. The semantics for PATCH allows for partial updates, whereas PUT requires a complete replacement. Changes: * adds config.default_method_for_update you can set to :patch * optionally use PATCH instead of PUT in resource routes and forms * adds the #patch verb to routes to detect PATCH requests * adds #patch? to Request * changes documentation and comments to indicate support for PATCH This change maintains complete backwards compatibility by keeping :put as the default for config.default_method_for_update.
* Add convenience method to hide a generator from the available onesCarlos Antonio da Silva2012-02-031-0/+6
| | | | | | It is usually useful to be able to hide a generator when running rails generate command. Such generators might be used only to dry up generators code and shouldn't be available to end users.
* Use https://rubygems.org source for default GemfileGuillermo Iguaran2012-02-011-1/+1
| | | | See https://github.com/rails/rails/pull/4684#commitcomment-920313
* Merge pull request #4825 from sikachu/master-fix-plugin-newJosé Valim2012-02-011-1/+1
|\ | | | | Fix broken test introduced from #4814
| * Fix broken test introduced from #4814Prem Sichanugrist2012-02-011-1/+1
| | | | | | | | | | | | * ruby_debugger_gemfile_entry was removed from the generator. Please make sure to run `grep` or `ack` to make sure it was removed in every places.
* | Fix GH #4737. Missing helper file (LoadError) in mountable plugin.kennyj2012-02-021-1/+3
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 10:49:14 +0000