blocks|key|1958387|text|首先是预置，我喜欢将我的heroku+git遥控器设置为暂存和生产，这样您就可以轻松地使用git推送暂存/生产来部署到其中的每一个。我将使用该设置来解释如何创建登台环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1958388|1958389|创建一个config/environments/staging.rb，您可以将其复制下来作为临时数据库的database.yml条目(+heroku实际上并不需要，但也不会有什么坏处)|ordered-list-item|offset|length|style|CODE|1958390|备份您的配置文件(如果您有的话)|1958391|通过将您的环境设置从heroku(生产服务器)复制到.env文件，并将这些值添加到配置中：RACK_ENV=staging+RAILS_ENV=staging因此它将使用带有推送的heroku环境的登台环境(这些是您想要的heroku应用程序名，而不是production/staging)|1958392|Do+a‘heroku+configuration.|1958393|fork+:production/staging)|1958394|Do+--remote+staging’|1958395|请确保将代码正确部署到登台环境|1958396|1958397|您也可以阅读本教程，我想我是用它来开始在heroku上使用多个环境的：https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations|1958398|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations^0|0|0|4|U|0|0|19|Y|0|0|0|0|0|0|Z|2Y|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|18|8|@$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|1B|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|1F|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1G|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|1H|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|1I|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1K|8|@]|9|@$F|1L|G|1M|1|1N]]|A|$]]|$1|Y|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

First the predispositions, i like to have my heroku git remotes set up as staging and production so you can easily use git push staging/production to deploy to each one of them. I'll be using that setup to explain how to make a staging env.

<ol>
<li>create a <code>config/environments/staging.rb</code> which you will copy off `config/environments/production.rb'</li>
<li>add a database.yml entry for the staging database(not really needed for heroku but can't hurt)</li>
<li>Backup your .env file (if you have it)</li>
<li>Install heroku-config plugin by <code>heroku plugins:install git://github.com/ddollar/heroku-config.git</code></li>
<li>pull your environment settings from heroku(production server) with <code>heroku config:pull --remote production</code></li>
<li>make changes to the .env file and don't forget to add these values to the config: <code>RACK_ENV=staging RAILS_ENV=staging</code> so it will use the staging environment configuration.</li>
<li>fork a heroku environment with <code>heroku fork -a production staging</code> (those are heroku appnames you want instead of production/staging)</li>
<li>Do a `heroku config:push --remote staging'</li>
<li>Be sure to deploy the code to staging env properly</li>
</ol>

You can also read this tutorial, i think i used it to get started with multiple envs on heroku:
<a href="https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations" rel="noreferrer">https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations</a>

blocks|key|1958432|text|我发现heroku+fork+-a+PRODUCTION_APP_NAME+NEW_STAGE_APP_NAME是一种更快、更简单的方法。它创建新的应用程序，复制所有内容(包括postgres数据库)。然后，当有意义时，我手动将插件降级为较小的计划(例如，入门级数据库)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1958433|事实上，我们开始使用相对较新的heroku+pipeline:promote来自动(并且非常快速地)将编译后的插件从试运行推送到生产环境。(假设您通过设置或环境变量设置了任何特定于环境的设置，因此代码段是相同的。)|1958434|entityMap^0|3|1H|0|F|N|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I found the <code>heroku fork -a PRODUCTION_APP_NAME NEW_STAGE_APP_NAME</code> to be a faster, easier way to do it... it creates the new app, copies everything (including the postgres database). Then I went in and manually downgraded the addons to smaller plans when it made sense (for example, a starter tier database).

In fact, we started using the relatively new <code>heroku pipeline:promote</code> to manage automatically (and VERY quickly) pushing a compiled slug from staging to production. (That assumes you have any env-specific settings via settings or environment variables, so the code slug is the same.)

blocks|key|2793559|text|请注意，根据Heroku网站上的以下指南，不建议使用berislavbabic解释的过程：https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2793560|您可以在那里详细阅读，但建议您保持登台环境与生产环境相同，并简单地使用heroku+fork从生产环境复制到登台环境。|2793561|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations^0|19|2Y|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Note that the procedure explained by berislavbabic is not recommended according to the following guide on Heroku's site: <a href="https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations" rel="nofollow">https://devcenter.heroku.com/articles/multiple-environments#managing-staging-and-production-configurations</a>

You can read in detail there, but the recommendation is to keep the staging environment the same as the production environment and simply use heroku fork to copy from production to staging.

I currently have two environments in which I work: <code>development</code> locally and <code>production</code> on Heroku. 

I would like to add a <code>staging</code> environment on Heroku to see that everything goes as expected before pushing the app live to users. Preferably, the <code>staging</code> environment should have the exact same settings and data as the <code>production</code> environment.

What are the steps needed to accomplish the above?

Adding a staging environment to the workflow

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我目前有两个工作环境:本地的development和Heroku上的production。我想在Heroku上添加一个staging环境，看看在将应用程序实时推送给用户之前，一切都按预期进行。优选地，staging环境应该具有与production环境完全相同的设置和数据。完成上述任务需要哪些步骤？

问将过渡环境添加到工作流
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将过渡环境添加到工作流EN