我们成功在 Digital Ocean 上安装了 Discourse，一切运行正常，但我们无论如何都找不到 Discourse 的实际文件在哪里。我们想测试一些修改并构建一些插件，但找不到任何文件。我们使用 FileZilla 登录到服务器，但无论如何都找不到 Discourse 应用程序文件，例如 discourse/app。我们进入了 var/discourse 文件夹，但什么都没有。然后进入 var/discourse/containers，也什么都没有。我们尝试通过 SSH 运行 .launcher 进入 app，在终端中可以看到我们的文件位于 var/www，但当我们登录服务器时，该目录并不存在。我们还尝试了 var/lib/docker/containers，同样什么都没有。Discourse 文件究竟位于哪里？谢谢。
1 个赞
That is how Docker works, the actual files are inside a Docker container, and therefore “invisible” using Filezilla.
If you want to test modifications to Discourse, like plugins and themes, you won’t be able to do it in a production install.
For themes check Beginner's guide to using Discourse themes
For plugins Beginner's Guide to Creating Discourse Plugins - Part 1
1 个赞
Is there another way to install this other than using docker then? I have read all the guides, but it’s kind of difficult to develop with invisible files.
1 个赞
The paradigm is very different from the 90’s PHP applications, where it was normal to edit files in production servers using FTP.
Changes to Discourse behavior are supposed to be separate projects, living in a git repository of their own, and to make use of the existing plugin and theme APIs.
So let’s say you want to add an extra field to the topic composer where a user will add their preferred color. You will create a new Discourse plugin following Beginner's Guide to Creating Discourse Plugins - Part 1, then put that on GitHub in a repository named discourse-favorite-color and install that to your instance using Install Plugins in Discourse
3 个赞
OK, got it. Will have to get used to this new way to develop. Just curious, every time we add a plugin we need to ./launcher rebuild app? And then do that again when modify the plugin?
1 个赞
Yes.
However, that is something that should happen infrequently, as that is your production install.
For development and test purposes, the very first part of Beginner's Guide to Creating Discourse Plugins - Part 1 tells you to setup a “Development Environment” where you can do changes and test just refreshing your browser.
1 个赞
That’s what I do, though you can also do an upgrade via the web interface at /admin/upgrade.
Also, a 2-container install lets you upgrade like
./launcher bootstrap web_only
./launcher destroy web_only; ./launcher start web_only
so your site is down just as long as it takes the new server to boot up (about a minute).
2 个赞