Skip to content

Commit

Permalink
Replace secrets with credentials in comments
Browse files Browse the repository at this point in the history
In comments in templates for `config/database.yml`, there is a
reference to `secrets.yml` which is now deprecated.
They should be replaced with `credentials.yml` so that everyone
using latest Rails can understand.
  • Loading branch information
okuramasafumi committed Jan 11, 2019
1 parent 7d7a952 commit f897263
Show file tree
Hide file tree
Showing 9 changed files with 9 additions and 9 deletions.
Expand Up @@ -24,7 +24,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -60,7 +60,7 @@ test:
<<: *default <<: *default
database: <%= app_name[0,4] %>_tst database: <%= app_name[0,4] %>_tst


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -54,7 +54,7 @@ test:
<<: *default <<: *default
url: jdbc:db://localhost/<%= app_name %>_test url: jdbc:db://localhost/<%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -27,7 +27,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -43,7 +43,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -32,7 +32,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -33,7 +33,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -59,7 +59,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down
Expand Up @@ -26,7 +26,7 @@ test:
<<: *default <<: *default
database: <%= app_name %>_test database: <%= app_name %>_test


# As with config/secrets.yml, you never want to store sensitive information, # As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is # like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database. # ever seen by anyone, they now have access to your database.
# #
Expand Down

0 comments on commit f897263

Please sign in to comment.