现有服务器安装说明

[khionu (Khionu Sybiern)]

我找到了一些帖子，例如这篇，其中有人希望在现有服务器上安装 Discourse。我尝试整合相关资源，但在这实例与 GitHub 之间来回查阅五个不同的来源，过程令人头疼。这真是一段曲折的经历，我强烈建议您在脚本中增加更多功能以支持此类用例。

我尚未解决的最后问题是 app.yml 的最终结构。目前我只找到了一些片段，不足以确认我已整合的内容是否完整。我建议 launcher 脚本能够直接生成副本，而无需额外步骤。这一改进将允许用户预先配置所有所需内容。目前，如果能提供原始文件模板的链接，或者在回复中附上该模板，我将不胜感激。

[codinghorror (Jeff Atwood)]

There are many, many good reasons we only officially support the docker based install method.

This will not be changing.

[Falco]

@khionu

The last thing I have yet to figure out is the final structure of app.yml . I have found fragments only, and not enough to conclude that what I’ve compiled is everything.

It’s right here: discourse_docker/samples/standalone.yml at master · discourse/discourse_docker · GitHub

@khionu

where people have wanted to install Discourse on an existing server. I’ve attempted to pull the pieces together, but this has been a headache going between 5 different sources between this instance and the GitHub. This has been a ride, and I would highly recommend adding more to your scripts to support this use case.

Using the sample file I provided above, comment out the lines about exposed ports (since this server is shared they will already be busy). After that add this line to the template list on the top:

- "templates/web.socketed.template.yml"

Now, after a rebuild Discourse will be listening only on a Unix socket under the shared folder. Point your reverse proxy to that.