Okay, so if I already have a well-developed plugin in development mode, how do I move that plugin to production without relying on third-party services? Is there even a way to do that?

So you recommend Discourse team move away from GitHub? There are several alternatives and that’s fine. Use them if you must, but if you aren’t prepared to put in a little work, don’t bother running Discourse imho.

Is that what you call combative? I’m sorry, but nobody’s been fighting, you’re probably just being too sensitive. And I’m sorry if that sounded combative. Anyway, to answer your question, I obviously did it with a disposable GitHub account, but they’re so small that I don’t really have to test them too much or write much code. I’ve already installed them using the disposable account and tested that they work, but in the long run, I don’t want to have to keep an eye on the repository every time I want to make a change. I’m not kidding when I say they’re very small. For example, one of them just adds a button to an external page on the home page, and that’s it.

It’s like saying you want a car, but can’t be bother getting the annual road-worthiness check. It’s just the cost of doing business when hosting publicly on the open web. I’m sure if you want to, you can work out a way to modify the install scripts and symlink them from somewhere on your server, but you don’t sound as if you want to do any work and it will be on you to write and support that solution. [图片] Willy: . I’m not kidding when I say they’re very small. For example, one of them just adds a button to an external page on the home page, and that’s it. If you can boil that down to a Theme Component you could go Heath Robinson and use discourse_theme to push from your local machine to your server, but don’t cry if your local machine dies, is lost or stolen and you can’t get your code back (without then working out how to get a live copy from your server) [图片] Install the Discourse Theme CLI console app to help you build themes Developer Guides The [discourse] Discourse Theme CLI is a ruby gem that allows you to use your editor of choice when developing Discourse themes and theme components. As you save files the CLI will update the remote theme or component and changes to it will appear live! Installing To play with it, make sure you have Ruby 2.5 or up installed. [image] If you are on Windows, you have 2 options: Option 1: Windows Subsystem for Linux. Windows 10 has access to a full Linux environment, you can use it to install …

Even simpler if you don’t want to install the discourse_theme gem, themes can be uploaded as a zip file and you could build quite a lot in the admin UI directly. And to reiterate, unless you’re working with ruby you don’t need a plugin at all, so a theme is likely what you’re asking for… no git needed.

Good point! But the advantage of discourse_theme is the instant way it updates in place so you can quickly checkout changes without having to zip an update and re-upload.

[图片] merefield: It’s like saying you want a car Sounds more like wanting to drive a car but never visit a gas station. “I’ll just scoop the gas into the tank using my bare hands”. :fire: If you used GitHub to develop the plugins then using it as a source for installation is trivial. Pushing changes to a repo is less effort than transferring updated plugin files manually to a server. It sounds more like you’re trying to bypass the installation process to deploy plugins on a Hosted Discourse installation.

[图片] Willy: I’m not kidding when I say they’re very small. For example, one of them just adds a button to an external page on the home page, and that’s it. I am wondering if you mean #plugin or #theme-component ? For example the custom button on Home screen, could be accomplished with a #theme-component . A TC can be laid out in a zip file(maybe best route to have full TC structure) or even entered in creating it/inputting code in the Create Theme component using the internal use.

(Btw @Heliosurge I think this was brought up earlier): [图片] merefield: [图片] Willy: . I’m not kidding when I say they’re very small. For example, one of them just adds a button to an external page on the home page, and that’s it. If you can boil that down to a Theme Component you could go Heath Robinson and use discourse_theme to push from your local machine to your server, but don’t cry if your local machine dies, is lost or stolen and you can’t get your code back (without then working out how to get a live copy from your server) [图片] awesomerobot: Even simpler if you don’t want to install the discourse_theme gem, themes can be uploaded as a zip file and you could build quite a lot in the admin UI directly.

It’s obvious that the topic has now completely veered off course, as always happens in any thread that goes against the grain. I don’t even intend to discuss the issue of using a theme component, but thanks to everyone anyway.

How did it veer off track? You asked a question and people expressed their opinions. Looks completely on topic to me? You have all the info you need now to implement whatever setup you want?

如何在不使用第三方主机的情况下安装插件？

产品支持安装

Falco (Falco) 2026 年6 月 25 日 18:13 27

你可以在 app.yml 中使用卷支持功能，将主机上的文件夹挂载到容器的插件文件夹。

话题		回复	浏览量
Install plugins on a self-hosted site Self-Hosting how-to	42	266471	2026 年3 月 10 日
Why can't I install plugins locally? Self-hosting	8	332	2026 年6 月 5 日
Installing new plugins Product Support	3	921	2023 年8 月 18 日
Install plugins without direct access to github Product Support unsupported-install	12	1544	2019 年3 月 18 日
Trying discourse and plugins for github Product Support	14	458	2025 年2 月 5 日

如何在不使用第三方主机的情况下安装插件？

相关话题