| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
* origin/master:
Removal of javascript related gems when creating an app
Conflicts:
railties/lib/rails/generators/app_base.rb
|
| |\
| | |
| | | |
Removal of javascript related files when creating an app
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit 0417bc8 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.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Prepare generated Gemfile for Capistrano 3
|
| |
| |
| |
| |
| |
| |
| | |
Capistrano 3 is now rails-less, so we need to encourage developers to use capistrano-rails gem.
More details: http://www.capistranorb.com/documentation/frameworks/ruby-on-rails/
[ci skip]
|
|/ |
|
|\
| |
| | |
Add note about database connection pool in postgres template
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Small refactoring changes to generators.
Conflicts:
railties/lib/rails/generators/rails/controller/controller_generator.rb
|
| |
| |
| |
| |
| | |
Made a method name clearer (added a bang to the end to show that it
mutates arguments) and extracted indentation into its own method.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this commit options for `rails new` and `rails plugin new` had to
be passed in a strict order, trying to execute a following command:
rails new -J path/to/app
resulted in an error.
This commit fixes the situation and allows to pass path to app anywhere
after `new`
|
| |
| |
| |
| | |
This reverts commit ba0407337e93c4ef55cef3472143f62e8a984a64.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, our default HTML would validate properly, but would generate
a warning: it doesn't declare a character encoding.
According to [the spec][encoding-spec], if you don't specify an
encoding, a 7 step algorithm happens, with a toooon of sub-steps. Or, we
could just actually specify it.
Since everything else in Rails assumes UTF-8, we should make sure pages
are served with that encoding too. This meta tag is the simplest way to
accomplish this.
More resources:
* http://blog.whatwg.org/the-road-to-html-5-character-encoding
* http://www.w3.org/International/tutorials/tutorial-char-enc/
* http://validator.w3.org/
[encoding-spec]: http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#determining-the-character-encoding
|
|/
|
|
| |
[John J. Wang & Prathamesh Sonpatki]
|
|
|
|
|
|
|
| |
The defaults hash isn't used unless the +class_options+ hash has a
particular key, so we don't need to compute it unless this is true.
Also moving some code for extracting a module into its own method.
|
|
|
|
|
|
|
|
|
|
| |
When creating a new application using the default rails generator
(`rails new my_app`), it will apply some permissions bypassing the
current process umask. The `bin' directory and any files inside it will
always be set a mode of 0755.
This change removes the current umask bits from the mode applied by
the generator on the `bin' directory and its content.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
_form view [Fixes #11573]
|
| |
|
| |
|
|
|
|
| |
rake task included in test:all rake task.
|
|\
| |
| | |
Remove unnecessary string interpolation
|
| |
| |
| |
| | |
Removed from controller template of scaffold generator.
|
|/
|
|
|
|
| |
Before the AppGenerator is started, ARGV needs to be modified to
correctly account for some things. I'm extracting these out into their
own class.
|
| |
|
|
|
|
| |
favor of `ActiveRecord::Generators::ActiveModel#update`
|
|\
| |
| | |
Change Rails Migration generator module to use AS::Concern
|
| |
| |
| |
| | |
railties/lib/rails/generators/migration.rb file
|
|/
|
|
|
| |
There are historical reasons that the `plugin` command was `plugin_new`, now those are no longer applicable, we should remove the naming edge case from the project. This PR is based off of comments from #11176
ATP Railties
|