> For the complete documentation index, see [llms.txt](https://ploegert.gitbook.io/til/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ploegert.gitbook.io/til/programmy/rails/access-secrets-in-a-rails-5-2-app.md).

# Access Secrets In A Rails 5.2 App

For a long time the access chain for getting at secrets in your Rails app stayed the same. For instance, getting at the `secret_key_base` value looked something like this:

```ruby
Rails.application.secrets.secret_key_base
```

In the world of Rails 5.2, secrets are no longer secrets. They are now credentials. This means they are under the `credentials` key instead of the `secrets` key. Here is how you can access `secret_key_base` now:

```ruby
Rails.application.credentials.secret_key_base
```

[source](https://www.engineyard.com/blog/rails-encrypted-credentials-on-rails-5.2)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ploegert.gitbook.io/til/programmy/rails/access-secrets-in-a-rails-5-2-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.