| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Tagged logging for which Rails has support since [3.2](http://guides.rubyonrails.org/3_2_release_notes.html#tagged-logging).
It is trivial & useful but unless somebody explicitly searches API docs, he/she may not know about it.
Hence, I added it in guides.
|
|
|
|
| |
<pre> block.
|
|
|
|
|
|
|
|
|
| |
Changed the title of the 3.5 chapter from "Using the change Method" to
"When to Use the change Method" since the chapter tells the migration
definitions supported by the change method. This fix the duplicate ID in the
document.
I've also changed some of the titles to respect the Guides guidelines.
|
|
|
|
| |
skip]
|
|
|
|
| |
erb tag wasn't closed well
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In chapter 2.4 there was an underscore at the start of the attr_readonly method name,
this underscore was interpreted as the opening of the <em> tag but it wasn't closed.
Worst, the underscore in self.class.serialized_attributes (end of paragraph)
was interpreted as the closing of the <em> tag and not as the name of a method.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This reverts commit fc80ebb13328eb5f233f65408ba281bf0f8ce68e.
Such changes aren't allowed in docrails.
|
| | |
|
| |
| |
| |
| | |
SessionHash isn't a thing, and tenses are wrong.
|
| | |
|
| |\
| | |
| | | |
Fixed little mistake in the docs
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
The example is about a Person model, say that "params[:model] would usually be a
hash of all the attributes for the person to create" could be confusing.
I changed to params[:person] since the example is about a Person creation.
|
| |\
| | |
| | | |
Added a bullet for :enable_starttls_auto in the smtp_settings table
|
| | | |
|
| | |
| | |
| | |
| | | |
incorrectly using symbol instead of string
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Per https://github.com/lifo/docrails/commit/e94e8d8c3fcac624466afcf61f6a118abe5a6af4#commitcomment-1784677
Thanks @randomecho!
This reverts commit e94e8d8c3fcac624466afcf61f6a118abe5a6af4.
|
| | | |
|
| |\ \
| | | |
| | | | |
minor update to asset_pipeline docs describing apache config
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
In the text there is a section about how to serve the assets with
far-future headers. The snippet that is proposed doesn't work on Ubuntu
11 (probably others) as mod_expires is not enabled out-of-the-box. I
noted this, and gave an example of how to load mod_expires with a2enmod.
|
| |\ \
| | | |
| | | | |
Added clairifications for default security headers.
|
| |/ / |
|
| |\ \
| | | |
| | | | |
Default headers description
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | | |
think that a quoted string will be better as it will automatically
escape double-quotes as well
|
| | |
| | |
| | |
| | |
| | | |
after running, git add .
do not need -a option to git commit
|
| | |
| | |
| | |
| | |
| | | |
Correct :error -> :alert, mention FlashHash class, mention that
you're not limited to notices and alerts, clean up.
|
| |\ \
| | | |
| | | | |
Fix rake guides:validate
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If the validation of a guide encounters an exception, inform about it
and continue with the loop to validate the rest.
|
| |/ /
| | |
| | |
| | | |
This rake task was looking for the output folder in the wrong place.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
directory; add exception handling"
This kind of changes should go on a pull request instead.
This reverts commit ecae2f0ef0452f8d333525a6aed58e5ab8d3ccb1.
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
add exception handling
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The app generator is not generally run under bundler, but the Bundler
constant is used here.
In particular you cannot create --dev apps without this.
|
| | | |
|
|\ \ \
| | | |
| | | | |
ActionView decoupling and sprockets-rails tests fail
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Method invalid_asset_host! was delegated to controller but sprockets
compile assets in their own scope without controller. And if we set asset_host
with second parameter it should raise error through invalid_asset_host!.
But since controller is nil it cannot be reached.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Option to run `bundle install` after generating new appplication was
added recently to rails. Since introduction, it contained a subtle bug
that caused it to use `Gemfile` from current directory (if it exists)
rather than from generated directory. This also accidentaly caused
railties tests to work without any problems - after generating test app
it just used `Gemfile` from the repository, rather than the one in
generated app. After fixing the bug mentioned above, this of course
broke. The easiest way to bypass that is to not generate a `Gemfile` for
test application - with such setup Bundler will just use first available
`Gemfile` in one of the parent directories.
|
| | | |
|