blocks|key|3996303|text|虽然@dhh和@morgoth+promise+to+add+environment+management+to+Rails+6，我用这种方式解决了我的任务，看起来一切都很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3996304|#+application.rb
class+Application+<+Rails::Application
++++if+Rails.env.development?
++++++++ENV["access_key_id"]+=+Rails.application.credentials.DEV_aws[:access_key_id]
++++++++ENV["secret_access_key"]+=+Rails.application.credentials.DEV_aws[:secret_access_key]
++++++++ENV["s3_bucket_name"]+=+Rails.application.credentials.DEV_aws[:s3_bucket_name]
++++end
++++if+Rails.env.production?
++++++++ENV["access_key_id"]+=+Rails.application.credentials.PROD_aws[:access_key_id]
++++++++***
++++end
end|code-block|syntax|javascript|3996305|所有内容都已就位并加密|3996306|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/rails/rails/pull/33521^0|G|1C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

While @dhh and @morgoth <a href="https://github.com/rails/rails/pull/33521" rel="nofollow noreferrer">promise to add environment management to Rails 6</a>, I solved my task this way, and all looks like working good: 

<pre><code># application.rb
class Application &lt; Rails::Application
 if Rails.env.development?
 ENV["access_key_id"] = Rails.application.credentials.DEV_aws[:access_key_id]
 ENV["secret_access_key"] = Rails.application.credentials.DEV_aws[:secret_access_key]
 ENV["s3_bucket_name"] = Rails.application.credentials.DEV_aws[:s3_bucket_name]
 end
 if Rails.env.production?
 ENV["access_key_id"] = Rails.application.credentials.PROD_aws[:access_key_id]
 ***
 end
end
</code></pre>

All is in on place and encrypted

blocks|key|3996337|text|我相信这个想法不是在你的凭证文件中有多个环境，而是有多个凭证文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3996338|我们通过使用credentials.dev.enc、credentials.production.enc等解决了这个问题。|offset|length|style|CODE|3996339|然后，我们将特定文件上载到特定服务器，作为部署过程的一部分。|3996340|这还允许您的环境拥有独立的主密钥和加密密钥，从而降低系统中的安全风险。|3996341|entityMap^0|0|6|J|Q|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

I believe the idea is not to have multiple environments in your credentials file, but to have multiple credentials files. 

We solved it by having <code>credentials.dev.enc</code>, <code>credentials.production.enc</code>, etc.

Then we upload the specific file to the specific server as part of the deploy process. 

This also allows your environments to have independent master keys and encryption keys, which reduces the security risks in your system.

blocks|key|3999297|text|我发现rails-env-credentials的gem对此很有用。不确定它与即将到来的Rails+6支持的兼容性如何，但它在我的应用程序上工作得很好。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3999298|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/sinsoku/rails-env-credentials^0|3|L|3|L|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

I've found the <a href="https://github.com/sinsoku/rails-env-credentials" rel="nofollow noreferrer"><code>rails-env-credentials</code></a> gem useful for this. Not sure how compatible it will be with the upcoming Rails 6 support but its been working great for my app.

blocks|key|3999351|text|Sampson+Crowley+on+Rails-talk+list：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3999352|对于Rails5，只需将特定于环境的凭据嵌套在所述环境的键下|3999353|然后，当访问所述配置时，您所要做的就是将环境添加到引入配置的参与方，例如：|3999354|credentials.yml.enc：|3999355|main_key:开发:+sub_key:+value_key：‘开发’生产:+sub_key:+value_key：‘生产’测试:+sub_key:+value_key：‘测试’|3999356|代码：|3999357|my_credential+=+Rails.application.credentials.dig(:main_key,+Rails.env.to_sym,+:sub_key,+:value_key)|code-block|syntax|javascript|3999358|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|Y|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Sampson Crowley on Rails-talk list:

for rails 5, just nest environment specific credentials under a key for said environment

then all you have to do when accessing said config is add the environment to the party that pulls in config, e.g.:

credentials.yml.enc:

main_key:
 development:
 sub_key:
 value_key: 'development'
 production:
 sub_key:
 value_key: 'production'
 test:
 sub_key:
 value_key: 'test'

code:

<pre><code>my_credential = Rails.application.credentials.dig(:main_key, Rails.env.to_sym, :sub_key, :value_key)
</code></pre>

I'm (still/always) new to Rails. While I was building my project Rails upgraded to v5.2 with <a href="https://guides.rubyonrails.org/security.html#custom-credentials" rel="nofollow noreferrer">encrypted credentials</a>. Now I'm about to deploy to production and found that I do not understand how to separate production credentials from development. And I'm not sure that I know how I would do it in v5.1. So how to make it in Rails 5.2?

How to manage credentials for different environments in Rails 5.2?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我(仍然/总是)是Rails的新手。在我构建我的项目时，Rails使用升级到了v5.2。现在我正要部署到生产环境中，我发现我不知道如何将生产凭证与开发分开。我不确定我是否知道在v5.1中我会如何做到这一点。那么如何在Rails 5.2中实现它呢？

问如何在Rails 5.2中管理不同环境的凭据？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Rails 5.2中管理不同环境的凭据？EN