Creating a duplicate of production environment

支持 安装
21

@RemahI didn’t say development - I said “staging/testing”. I’m talking about a staging environment to test things such as an importation of messages from another platform, etc.

No, I am not spamming the forum. This is a different thought process altogether. What you mention is regarding a backup problems or flaw that exists in the system and the standard “backup/restore” path that some might consider as an option to this path, however it is not the only path to follow and therefore I’m exploring another option of setting up such a staging environment presently by going down an altogether different path.

22

My comment was pointed: I said “developer” because you have “developed” a non-standard Discourse install.

We know that such configurations generate a lot of issues that are not relevant to the majority of instances using the officially supported install method.

I referred to the topic you created because it is a case in point.

Remember this topic. It is not a discussion of variations from the norm but a request for standard steps:

Your instance is a long way from such standard set of steps:

This topic becomes muddied the more unsupported configurations that are included here. The official install has a population of hundreds or thousands where advice will generally be applicable to all. Whereas non-standard installs often have a population/sample size of one so it is far better to put them in separate topics because some advice will be misleading for the majority.

23

I apologise if I’ve come across too strongly. :slightly_smiling_face:

I’m not trying to dissuade you from posting what is likely to be very useful information for some sites. Your contribution will be more useful and more easily referenced with its own title in its own topic.

24

令人困惑的是，我遇到了以下错误：

$ git reset --hard '28032eaf38530b96c92aef3df42841aa8613a2f6'
fatal: 无法解析对象 '28032eaf38530b96c92aef3df42841aa8613a2f6'。

我相信这个哈希值正是我生产服务器上正在运行的版本，而且在 GitHub 上看起来也是存在的：https://github.com/discourse/discourse/commits/28032eaf38530b96c92aef3df42841aa8613a2f6

其他方面看起来都很正常：

$ git status
# 在 master 分支上
没有要提交的内容，工作目录干净
$ git fsck
检查对象目录：100% (256/256)，完成。
检查对象：100% (5038/5038)，完成。

我想将升级计划到 2.7.0.beta2，但这似乎阻止了我从与生产服务器相同的起点开始：:frowning:

25

哦——我把 Discourse 的哈希值和 discourse-docker 的哈希值搞混了……真傻。我应该按照 How do you install an earlier version of Discourse? - #2 by johnmuhl 的说明，将我的 Discourse 版本哈希值放入 yml 文件的 version: 字段中。

抱歉打扰大家了。