<i id='kowLN'><tr id='kowLN'><dt id='kowLN'><q id='kowLN'><span id='kowLN'><b id='kowLN'><form id='kowLN'><ins id='kowLN'></ins><ul id='kowLN'></ul><sub id='kowLN'></sub></form><legend id='kowLN'></legend><bdo id='kowLN'><pre id='kowLN'><center id='kowLN'></center></pre></bdo></b><th id='kowLN'></th></span></q></dt></tr></i><div id='kowLN'><tfoot id='kowLN'></tfoot><dl id='kowLN'><fieldset id='kowLN'></fieldset></dl></div>

<small id='kowLN'></small><noframes id='kowLN'>

    1. <tfoot id='kowLN'></tfoot>
    2. <legend id='kowLN'><style id='kowLN'><dir id='kowLN'><q id='kowLN'></q></dir></style></legend>
        • <bdo id='kowLN'></bdo><ul id='kowLN'></ul>

        在开发、登台和生产之间同步 Drupal 站点

        Syncing Drupal site between dev, staging and production(在开发、登台和生产之间同步 Drupal 站点)
        <tfoot id='iteCd'></tfoot>
            <bdo id='iteCd'></bdo><ul id='iteCd'></ul>
            <legend id='iteCd'><style id='iteCd'><dir id='iteCd'><q id='iteCd'></q></dir></style></legend>

                  <tbody id='iteCd'></tbody>
                <i id='iteCd'><tr id='iteCd'><dt id='iteCd'><q id='iteCd'><span id='iteCd'><b id='iteCd'><form id='iteCd'><ins id='iteCd'></ins><ul id='iteCd'></ul><sub id='iteCd'></sub></form><legend id='iteCd'></legend><bdo id='iteCd'><pre id='iteCd'><center id='iteCd'></center></pre></bdo></b><th id='iteCd'></th></span></q></dt></tr></i><div id='iteCd'><tfoot id='iteCd'></tfoot><dl id='iteCd'><fieldset id='iteCd'></fieldset></dl></div>

                  <small id='iteCd'></small><noframes id='iteCd'>

                1. 本文介绍了在开发、登台和生产之间同步 Drupal 站点的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                  问题描述

                  通常在 Drupal (6.x) 站点启动后,人们开始注册并输入他们自己的内容.每当需要升级时,将生产数据库复制到 dev,然后在 dev 上完成开发,然后推送到暂存以供客户批准.

                  Often after a Drupal (6.x) site is launched, I have people starting to sign up and enter their own content. Whenever there is need for an upgrade, the database on production is copied to dev and then the development is done on dev, later get pushed to staging for client's approval.

                  当网站最终准备好上线时,就会出现问题.生产服务器具有最新的用户输入内容,开发和登台具有最新的功能.简单地在生产中覆盖数据库是行不通的.我通常做的是写下对开发所做的工作,然后按照步骤在生产中再次执行实现.随着系统变得越来越大,生产中的一个错误可能会导致业务损失.我无法关闭网站几个小时.我无法确定在给定时间有多少人在使用该网站,即使如此,也不可能等到网站上没有人再进行升级.

                  When the site is eventually ready to go live, there is a problem. Production server has the latest user inputted content, dev and staging have the latest functionality. Simply overwriting the database on production won't work. What I usually do is to write down what has been done to dev and than follow the steps to go though the implementations again on production. As the system grows bigger, one single mistake on production may cause lost of business. I can't shutdown the site for several hours. I can't tell how many people are using the site at a given time, even so it's impossible to wait for a time where nobody is on the site to make the upgrade.

                  有人有什么好主意吗?

                  提前致谢.

                  推荐答案

                  您需要研究两个概念:第一个是Exportables" 这通常是导出给定模块的所有配置的一种方式.第二个是Features"(名字很吓人,是的),这是一种将一组可导出对象分组到用于版本控制、更新、部署、回滚等的给定变更集.

                  There are two concepts you need to look into: The first is "Exportables" which is generally a way of exporting all the configuration of a given module. The second is "Features" (terribly named, yes) which is a way of grouping a set of Exportables into a given changeset for version control, updating, deployment, rollback, etc.

                  为了澄清起见,许多模块实现了他们自己的Exportables"方法,我在上面链接到的是 Exportables 模块.这是一个更广泛的策略 - http://www.sthlmconnection.se/tips-and-tweaks/exportable-configuration-your-drupal-module-ctools

                  For clarification, many modules implement their own "Exportables" methodology what I linked to above was the Exportables module. Here's a wider strategy for it - http://www.sthlmconnection.se/tips-and-tweaks/exportable-configuration-your-drupal-module-ctools

                  这篇关于在开发、登台和生产之间同步 Drupal 站点的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                  本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

                  相关文档推荐

                  DeepL的翻译效果还是很强大的,如果我们要用php实现DeepL翻译调用,该怎么办呢?以下是代码示例,希望能够帮到需要的朋友。 在这里需要注意,这个DeepL的账户和api申请比较难,不支持中国大陆申请,需要拥有香港或者海外信用卡才行,没账号的话,目前某宝可以
                  PHP通过phpspreadsheet导入Excel日期,导入系统后,全部变为了4开头的几位数字,这是为什么呢?原因很简单,将Excel的时间设置问文本,我们就能看到该日期本来的数值,上图对应的数值为: 要怎么解决呢?进行数据转换就行,这里可以封装方法,或者用第三方的
                  mediatemple - can#39;t send email using codeigniter(mediatemple - 无法使用 codeigniter 发送电子邮件)
                  Laravel Gmail Configuration Error(Laravel Gmail 配置错误)
                  Problem with using PHPMailer for SMTP(将 PHPMailer 用于 SMTP 的问题)
                  Issue on how to setup SMTP using PHPMailer in GoDaddy server(关于如何在 GoDaddy 服务器中使用 PHPMailer 设置 SMTP 的问题)

                    <legend id='mUAiJ'><style id='mUAiJ'><dir id='mUAiJ'><q id='mUAiJ'></q></dir></style></legend>
                        <tbody id='mUAiJ'></tbody>

                        <tfoot id='mUAiJ'></tfoot>
                        1. <i id='mUAiJ'><tr id='mUAiJ'><dt id='mUAiJ'><q id='mUAiJ'><span id='mUAiJ'><b id='mUAiJ'><form id='mUAiJ'><ins id='mUAiJ'></ins><ul id='mUAiJ'></ul><sub id='mUAiJ'></sub></form><legend id='mUAiJ'></legend><bdo id='mUAiJ'><pre id='mUAiJ'><center id='mUAiJ'></center></pre></bdo></b><th id='mUAiJ'></th></span></q></dt></tr></i><div id='mUAiJ'><tfoot id='mUAiJ'></tfoot><dl id='mUAiJ'><fieldset id='mUAiJ'></fieldset></dl></div>

                            <bdo id='mUAiJ'></bdo><ul id='mUAiJ'></ul>

                            <small id='mUAiJ'></small><noframes id='mUAiJ'>