TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Revert "Fixed a few grammar issues."

Browse Source 
This reverts commit 16ce41b7f4449d6df15df30d69aef18da6510f36.

Reason: See
16ce41b7f4 (commitcomment-14475125)
This commit is contained in:
Rafael Mendonça França 2015-11-18 13:47:45 -02:00
parent ce37df9cc1
commit a951d5b093
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
guides/source/caching_with_rails.md
View File

@ -100,7 +100,7 @@ called key-based expiration.
Cache fragments will also be expired when the view fragment changes (e.g., the
HTML in the view changes). The string of characters at the end of the key is a
template tree digest. It is a md5 hash computed based on the contents of the
template tree digest. It is an md5 hash computed based on the contents of the
view fragment you are caching. If you change the view fragment, the md5 hash
will change, expiring the existing file.

2
guides/source/configuring.md
View File

@ -723,7 +723,7 @@ $ bin/rails runner 'puts ActiveRecord::Base.configurations'
Here the connection information in `ENV['DATABASE_URL']` is ignored, note the different adapter and database name.
Since it is possible to embed ERB in your `config/database.yml` it is the best practice to explicitly show you are using the `ENV['DATABASE_URL']` to connect to your database. This is especially useful in production since you should not commit secrets like your database password into your source control (such as Git).
Since it is possible to embed ERB in your `config/database.yml` it is best practice to explicitly show you are using the `ENV['DATABASE_URL']` to connect to your database. This is especially useful in production since you should not commit secrets like your database password into your source control (such as Git).
```
$ cat config/database.yml