blocks|key|2463443|text|在rails引导时，使用dotenv将环境变量从.env[.<staging>]加载到env中，而不是在deploy.rb中导出环境变量。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2463444|请按照以下步骤操作：|2463445|将这一行添加到Gemfile的顶部：|2463446|gem+'dotenv-rails'|code-block|syntax|javascript|2463447|在deploy/production.rb中将.env.production文件放入linked_file中|2463448|set+:linked_files,+fetch(:linked_files,+[]).push('.env.production')|2463449|在远程主机上，将.env.production文件添加到包含以下行的shared文件夹中：|2463450|SECRET_KEY_BASE=<Your+secret>|2463451|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/bkeepers/dotenv^0|O|G|C|6|0|0|0|0|0|1|K|N|F|16|B|0|0|8|F|Y|6|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1C|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1K|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|U|3|V|5|L|7|1Q|8|@]|D|@]|E|$M|N]]|$1|W|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

Rather than exporting env variables in deploy.rb, use <a href="https://github.com/bkeepers/dotenv" rel="nofollow noreferrer">dotenv</a> to load environment variables from <code>.env[.&lt;staging&gt;]</code> into ENV when rails booting.

Follow these steps:

Add this line to the top of your Gemfile:

<pre><code>gem 'dotenv-rails'
</code></pre>

Put <code>.env.production</code> file into the <code>linked_file</code> in <code>deploy/production.rb</code>:

<pre><code>set :linked_files, fetch(:linked_files, []).push('.env.production')
</code></pre>

On the remote host, add the <code>.env.production</code> file in <code>shared</code> folder which contains this line:

<pre><code>SECRET_KEY_BASE=&lt;Your secret&gt;
</code></pre>

blocks|key|3683663|text|有一个gem可以用来完成这个任务：https://github.com/capistrano-plugins/capistrano-secrets-yml|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3683664|安装|style|BOLD|3683665|将此代码添加到Gemfile：|3683666|group+:development+do
++gem+'capistrano',+'~>+3.2.1'
++gem+'capistrano-secrets-yml',+'~>+1.0.0'
end|code-block|syntax|javascript|3683667|然后：|3683668|$+bundle安装|3683669|设置和使用|3683670|make+sure+your+local+config/secrets.yml+is+not+git+tracked.+It+should+be+on+the+disk,+but+gitignored.|3683671|在本地config/secrets.yml中填充生产密钥：|3683672|production:
++secret_key_base:+d6ced...|3683673|添加到Capfile：|3683674|require+'capistrano/secrets_yml'|3683675|通过执行以下任务在远程服务器上创建secrets.yml文件：|3683676|$+bundle+exec+cap+production+setup|3683677|您现在可以继续执行其他部署任务。|3683678|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/capistrano-plugins/capistrano-secrets-yml^0|H|1O|0|0|0|2|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|D|3|E|5|6|7|1M|8|@$A|1N|B|1O|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1P|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|1Q|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|1R|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1S|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1T|8|@]|9|@]|C|$]]|$1|U|3|V|5|L|7|1U|8|@]|9|@]|C|$M|N]]|$1|W|3|X|5|6|7|1V|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|L|7|1W|8|@]|9|@]|C|$M|N]]|$1|10|3|11|5|6|7|1X|8|@]|9|@]|C|$]]|$1|12|3|13|5|L|7|1Y|8|@]|9|@]|C|$M|N]]|$1|14|3|15|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|16|3|17|5|L|7|20|8|@]|9|@]|C|$M|N]]|$1|18|3|19|5|6|7|21|8|@]|9|@]|C|$]]|$1|1A|3|-4|5|6|7|22|8|@]|9|@]|C|$]]]|1B|$1C|$5|1D|1E|1F|C|$1G|1H]]]]

There is a gem for exactly this task:
<a href="https://github.com/capistrano-plugins/capistrano-secrets-yml" rel="nofollow noreferrer">https://github.com/capistrano-plugins/capistrano-secrets-yml</a>

Install

Add this to Gemfile:

<pre><code>group :development do
 gem 'capistrano', '~&gt; 3.2.1'
 gem 'capistrano-secrets-yml', '~&gt; 1.0.0'
end
</code></pre>

And then:

$ bundle install

Setup and usage

<pre><code>make sure your local config/secrets.yml is not git tracked. It should be on the disk, but gitignored.
</code></pre>

populate production secrets in local config/secrets.yml:

<pre><code>production:
 secret_key_base: d6ced...
</code></pre>

add to Capfile:

<pre><code>require 'capistrano/secrets_yml'
</code></pre>

create secrets.yml file on the remote server by executing this task:

<pre><code>$ bundle exec cap production setup
</code></pre>

You can now proceed with other deployment tasks.

blocks|key|3683680|text|您可以在shared/config中的服务器中创建名为application.yml的文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3683681|从以下解决方案中选择任何一种|3683682|deploy.rb中的以下代码将自动符号链接您的application.yml|3683683|set+:linked_files,+%25w{config/application.yml}|code-block|syntax|javascript|3683684|或|3683685|然后通过一个简单的capistrano任务将这个application.yml与您的current/config/application.yml进行符号链接。|3683686|entityMap^0|4|D|R|F|0|0|O|F|0|0|0|O|F|16|U|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|13|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|T|$]]

You can create a file in your server called <code>application.yml</code> in <code>shared/config</code>.

Choose any one of solution from bellow 

Following code in deploy.rb will automatically symlink your <code>application.yml</code>

<pre><code>set :linked_files, %w{config/application.yml}
</code></pre>

Or 

Then symlink this <code>application.yml</code> with your <code>current/config/application.yml</code> with a simple capistrano task.

blocks|key|544169|text|放弃环境变量，只是简单地读取一个文件。在secrets.yml中执行此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|544170|production:
++secret_key_base:+<%25=+File.read('/home/me/SECRET_KEY_BASE').strip+%25>|code-block|syntax|javascript|544171|然后制作秘密文件。|544172|$+rake+secret+>+~/SECRET_KEY_BASE|544173|在确定这个解决方案之前，我尝试从我的.bash_profile、.profile和.bashrc+(顶部和底部)导出秘密。我还尝试了PermitUserEnvironment和.ssh/environment。我不知道环境变量是如何从“环境”进入capistrano部署的。我运行ssh+example.com+printenv并查看了我的var。我登录后看到了我的var。但是美洲狮是从capistrano开始的..。它总是有它自己的环境。|544174|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Give up on environment vars and just simply read a file. Do this in secrets.yml.

<pre><code>production:
 secret_key_base: &lt;%= File.read('/home/me/SECRET_KEY_BASE').strip %&gt;
</code></pre>

Then make the secret file.

<pre><code>$ rake secret &gt; ~/SECRET_KEY_BASE
</code></pre>

Before settling on this solution I tried exporting the secret from my .bash_profile, .profile, and .bashrc (top and bottom). I also tried PermitUserEnvironment and .ssh/environment. I have no idea how an environment variable gets from "the environment" into a capistrano deployment. I ran ssh example.com printenv and saw my vars. I logged in and saw my vars. But puma started with capistrano... it always has it's own environment.

So I'm deploying to a Ubuntu droplet hosted on DigitalOcean a Rails 4 application running on Apache and Phusion Passenger. After deployment I've been getting 500s as a result of Rails production not finding the <code>secret_key_base</code> token for production. However, if I run an <code>echo $SECRET_KEY_BASE</code> it returns the rake secret generated by my deploy.rb.

The deploy.rb task to set that up is:

<pre><code>namespace :deploy do
 task :start do ; end
 task :stop do ; end

 desc "Setup ENV variables"
 task :env_vars do
 on "root@xxx.xxx.xxx.xx" do
 execute "export SECRET_KEY_BASE=#{`bundle exec rake secret`}"
 end
 end
end

before "deploy", "deploy:env_vars"
</code></pre>

However, Rails is still not picking it up. I even ssh'd into my server and in <code>rails console</code> checked and <code>ENV["SECRET_KEY_BASE"]</code> returns the correct secret token.

I thought using Capistrano's <code>:default_env</code> would work, but that only seems to set up environmental variables for the deploy task, but not actually on the server. Is there any easy way to solve this solution? My fallback is to just place the secret within <code>secrets.yml</code> since the repo is private, but I rather not do that.

Setting up secret_key_base on deploy with Capistrano 3

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

所以我正在部署一个托管在DigitalOcean上的Ubuntu droplet，一个运行在Apache和Phusion Passenger上的Rails4应用程序。在部署之后，由于Rails产品找不到用于生产的secret_key_base令牌，我得到了500。但是，如果我运行一个echo $SECRET_KEY_B...

问使用Capistrano 3在部署时设置secret_key_base
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Capistrano 3在部署时设置secret_key_baseEN