ProCourse インストーラー

[joebuhlig]

このプラグインは、サーバーにログインすることなく新しいプラグインを非常に簡単にインストールできるように設計されています。/admin/plugins/procourse-installer に以下の画面が追加されます。

そこから、プラグインの Git リポジトリの URL（.git を含めても含まなくても構いません）を入力し、「Install Plugin」をクリックします。インストールが完了するまで数分（約 5 分）お待ちください。完了すればすぐに使用可能です。

インストーラーを通じてインストールしたすべてのプラグインを表示したり、プラグインを削除したりするには、「Installed Plugins」に移動するだけです。

---

いくつかの注意点：

• これらのプラグインは、app または web_only の再構築やブートストラップを行っても残ります。

• 現在はマルチサイトインスタンスではテストされておらず、プラグインが機能するためにアプリケーションの /plugins ディレクトリへのアクセスが必要なため、そのようなシナリオでは失敗する可能性が高いです。

• インストールされたプラグインは /admin/plugins にも表示されます。

• これらのプラグインは /admin/upgrade から通常通りアップグレードできます。

• このプラグインの開発過程で、プラグインから翻訳を削除する際に潜在的なエラーが見つかりました。翻訳が使用されているページにユーザーがアクセスすると、サイトがエラーを表示する可能性があります。これは、admin/upgrade を使って特定のプラグインをアップグレードした場合でも、そのプラグインから翻訳が削除されていると発生するようです。現在、この問題の解決策を探っています。

---

要件：

• サポートされている Docker インストールを実行している必要があります。

• Docker Manager プラグインがインストールされている必要があります。

• /admin/upgrade へのアクセス権が必要です。

---

リポジトリはこちらです：

GitHub - procourse/procourse-installer: A Discourse plugin for installing other Discourse...

[pfaffman (Jay Pfaffman)]

Wow! That’s quite an accomplishment! I thought it couldn’t be done. Nice work, @joebuhlig!

EDIT: Here’s a question. If you do a rebuild at the command-line, are the procourse-installer plugins upgraded?

[justin (Justin DiRose)]

@pfaffman

If you do a rebuild at the command-line, are the procourse-installer plugins upgraded?

Yes – plugins should get upgraded upon bootstrap.

[Cozdabuch (cosmo)]

Just wow!
Nice work!

[itsbhanusharma (Bhanu Sharma)]

IMO, this deserves to be in core.

[Wedgebert (Will)]

So, would it be worth removing my existing plugins from the app.yml file and moving them to this installer?

[joebuhlig]

@itsbhanusharma

this deserves to be in core

I have to admit that I’m conflicted on this one. It would really cool to be in core but if it’s in core, installing plugins will only work on Docker installs and non-multisite installs. That would cause problems for a quite a lot of instances.

@Wedgebert

would it be worth removing my existing plugins from the app.yml file and moving them to this installer?

Technically, it doesn’t matter. They end up being installed in exactly the same way. This just makes it easier to do.

[itsbhanusharma (Bhanu Sharma)]

I assume the challenges associated with getting it to work with multisite are far more complex then getting to set up multisite (which none of my clients have deployed) and I’m saying that from managing over 2 dozen active discourse installations.

It should be easier to include this in the standard app.yml on bootstrap for the standalone installs and not including the same in a multisite/multi container/HA setup.

[Wedgebert (Will)]

@joebuhlig

I have to admit that I’m conflicted on this one. It would really cool to be in core but if it’s in core, installing plugins will only work on Docker installs and non-multisite installs. That would cause problems for a quite a lot of instances

It could always be part of core (with a big warning label that says “only works with docker”) but leave the current install method available as well.

Even better if there’s a way to detect a compatible installation and hide or show itself as necessary.

[joebuhlig]

@itsbhanusharma

I assume the challenges associated with getting it to work with multisite are far more complex then getting to set up multisite

The main challenge is precompiling assets and such. We’re effectively adding the repo to the /plugins and then running an docker manager upgrade on that specific plugin. That handles the magic side of it.

But in a multisite, you run into issues because you don’t want one instance to be able to make edits for all instances in the multisite.

[AndreSpecker (Andre Tiago)]

How i can uninstall a plugin using ssh? Because i installed Moderator Extension and now I cant put it anymore online, Error 502

[joebuhlig]

Assuming you can’t get to the admin panel:

1. SSH into the server.
2. cd /var/discourse
3. ./launcher enter app
4. vim /shared/tmp/procourse-installer/plugins.txt
5. Remove the offending plugin from the file.
6. exit
7. ./launcher rebuild app

[AndreSpecker (Andre Tiago)]

Cant up online

[joebuhlig]

Looks like your container isn’t running. Try this ./launcher start app

[AndreSpecker (Andre Tiago)]

Thank You, my error 502 now are resolved.

[Ellibereth]

I think the installer is working fine but I saw this in my error log, not sure if it’s anything but thought I’d might as well bring it up:

NameError (uninitialized class variable @@install_state in ProcourseInstaller::InstallController)
/var/www/discourse/plugins/procourse-installer/app/controllers/procourse_installer/install_controller.rb:4:in `status'

[joebuhlig]

Interesting. Do you have any guesses about what you were doing when that error came to be?

[BobbyZopfan (Bobby)]

Some 20 or so days ago, I installed this Procourse plugin, and another plugin (I forgot which one was it) thru this plugins interface.
After a few days, I found that many times (say once every few days) my website went dead slow. On those moments, even safe mode opening went equally slow. And after 20-30 minutes I found that the speed of my site became normal.

Although I have not got necessary skills to diagnose the logs, but since the logs’ (or was it sidekiq?) warning section contained ‘procourse’ so many times, I thought it is somehow related to this plugin installed inside/thru procourse plugin. So I uninstalled that plugin from procourse interface.

But yesterday it again (almost) crashed.
I checked and again found the word ‘procourse’ written in many many warnings in logs.

So today I decided and uninstalled procourse too.

Now my fingers are strongly crossed.

[joebuhlig]

Can you share the backtrace of one of those errors? That would help us narrow down where it’s coming from.

[BobbyZopfan (Bobby)]

Since I have Uninstalled the plugin for the time being. I can have the logs sent only when next occurrence occurs.

(I don’t know if logs are kept for 2-3 days or not, if they are, then I can try).

Thanks.