- 28 10月, 2013 1 次提交
-
-
由 Robin Dupret 提交于
Commit 0417bc83 add the coffee-rails and javascript runtime gems even when passing the --skip-javascript option but this is not the desired behavior. Also remove all javascript related stuff in the generated application such as the vendor/assets/javascripts folder.
-
- 22 10月, 2013 1 次提交
-
-
由 Robin Dupret 提交于
The application name is used to fill the `database.yml` and `session_store.rb` files ; previously, if the provided name contained whitespaces, it led to unexpected names in these files. Since Shellwords.escape adds backslashes to escape spaces, the app_name should remove them and replace any space with an underscore (just like periods previously). Also improve the assert_file helper to work with paths containing spaces using String#shellescape.
-
- 25 8月, 2013 1 次提交
-
-
由 Łukasz Strzałkowski 提交于
-
- 28 6月, 2013 1 次提交
-
-
由 Nikita Fedyashev 提交于
-
- 11 5月, 2013 1 次提交
-
-
由 Joe Kutner 提交于
-
- 04 5月, 2013 1 次提交
-
-
由 Nihad Abbasov 提交于
-
- 01 5月, 2013 1 次提交
-
-
由 wangjohn 提交于
syntax. This helps removing the class level abstraction of an application.
-
- 30 3月, 2013 1 次提交
-
-
由 Xavier Noria 提交于
-
- 29 3月, 2013 1 次提交
-
-
由 Trevor Turk 提交于
Allow transparent upgrading of legacy signed cookies to encrypted cookies; Automatically configure cookie-based sessions to use the best cookie jar given the app's config
-
- 25 3月, 2013 2 次提交
-
-
由 Jeremy Kemper 提交于
-
由 Gabe Kopley 提交于
v3 of pull request based on additional feedback from @jeremy
-
- 25 2月, 2013 2 次提交
-
-
由 Prem Sichanugrist 提交于
Ability to use a custom builder by passing `--builder` (or `-b`) has been removed. Consider using application template instead. See this guide for more detail: http://guides.rubyonrails.org/rails_application_templates.html
-
由 Yves Senn 提交于
We discussed that the auto explain feature is rarely used. This PR removes only the automatic explain. You can still display the explain output for any given relation using `ActiveRecord::Relation#explain`. As a side-effect this should also fix the connection problem during asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie` forced a connection.
-
- 01 2月, 2013 1 次提交
-
-
由 Akira Matsuda 提交于
so that the tester's local .railsrc file does not affect the test results
-
- 17 1月, 2013 1 次提交
-
-
由 Jeremy W. Rowe 提交于
application. EG: `rails new something.awesome.com` Conflicts: railties/CHANGELOG.md
-
- 11 1月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 08 1月, 2013 1 次提交
-
-
由 Xavier Noria 提交于
-
- 07 1月, 2013 1 次提交
-
-
由 Jeremy Kemper 提交于
Introduce ./bin for your app's executables: bin/bundle, bin/rails, bin/rake. Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'
-
- 06 1月, 2013 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 David Heinemeier Hansson 提交于
-
- 19 12月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 11 12月, 2012 1 次提交
-
-
由 schneems 提交于
This is an alternative implementation to #7771 thanks to the advice of @spastorino Rails is a dynamic framework that serves a static index.html by default. One of my first questions ever on IRC was solved by simply deleting my public/index.html file. This file is a source of confusion when starting as it over-rides any set "root" in the routes yet it itself is not listed in the routes. By making the page dynamic by default we can eliminate this confusion. This PR moves the static index page to an internal controller/route/view similar to `rails/info`. When someone starts a rails server, if no root is defined, this route will take over and the "dynamic" index page from rails/welcome_controller will be rendered. These routes are only added in development. If a developer defines a root in their routes, it automatically takes precedence over this route and will be rendered, with no deleting of files required. In addition to removing this source of confusion for new devs, we can now use Rails view helpers to build and render this page. While not the primary intent, the added value of "dogfooding" should not be under-estimated. The prior PR #7771 had push-back since it introduced developer facing files. This PR solves all of the same problems, but does not have any new developer facing files (it actually removes one). cc/ @wsouto, @dickeyxxx, @tyre, @ryanb, @josevalim, @maxim, @subdigital, @steveklabnik ATP Railties and Actionpack.
-
- 04 11月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 19 10月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 16 10月, 2012 1 次提交
-
-
由 Joshua Peek 提交于
-
- 15 10月, 2012 1 次提交
-
-
由 Robin Dupret 提交于
-
- 11 10月, 2012 1 次提交
-
-
由 Arun Agrawal 提交于
as it's removed here 1fc79546
-
- 10 10月, 2012 1 次提交
-
-
由 Mike Moore 提交于
Change the default test locations to avoid confusion around the common testing terms "unit" and "functional". Add new rake tasks for the new locations, while maintaining backwards compatibility with the old rake tasks. New testing locations are as follows: app/models -> test/models (was test/units) app/helpers -> test/helpers (was test/units/helpers) app/controllers -> test/controllers (was test/functional) app/mailers -> test/mailers (was test/functional)
-
- 02 10月, 2012 1 次提交
-
-
由 Guillermo Iguaran 提交于
-
- 22 9月, 2012 1 次提交
-
-
由 José Corcuera Z 提交于
-
- 17 9月, 2012 2 次提交
-
-
由 Guillermo Iguaran 提交于
-
由 Guillermo Iguaran 提交于
-
- 13 9月, 2012 1 次提交
-
-
由 Derek Prior 提交于
Users of other SCM's can now generate rails apps that will add the "empty" directories to source control, but will not have a useless .gitignore or mis-named .gitkeep files. * Change `rails new` and `rails plugin new` generators to name the `.gitkeep` as `.keep` in a more SCM-agnostic way. * Change `--skip-git` option to only skip the `.gitignore` file and still generate the `.keep` files. * Add `--skip-keeps` option to skip the `.keep` files. It closes #2800.
-
- 11 8月, 2012 2 次提交
-
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
It's not really a good idea to have this as a global config option. We should allow people to specify the behaviour per association. There will now be two new values: * :dependent => :restrict_with_exception implements the current behaviour of :restrict. :restrict itself is deprecated in favour of :restrict_with_exception. * :dependent => :restrict_with_error implements the new behaviour - it adds an error to the owner if there are dependent records present See #4727 for the original discussion of this.
-
- 08 8月, 2012 1 次提交
-
-
由 David Heinemeier Hansson 提交于
Revert "The application generator generates `public/humans.txt` with some basic data". I dont consider this something most people is going to want most of the time. If you want to add it in your own app, knock yourself out. But it doesnt belong in Rails imo
-
- 31 5月, 2012 1 次提交
-
-
- 14 5月, 2012 3 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 José Valim 提交于
-
由 Oscar Del Ben 提交于
-