Este plugin foi projetado para tornar extremamente fácil instalar novos plugins sem fazer login no servidor. Ele adiciona uma tela em /admin/plugins/procourse-installer que se parece com esta:
A partir daí, você pode inserir a URL (com ou sem .git) do repositório git do plugin e clicar em Instalar Plugin. Aguarde alguns minutos (cerca de 5 minutos) para que a instalação seja concluída e você estará pronto para usar.
Para ver todos os plugins que você instalou através do instalador ou para remover um plugin, basta ir para Plugins Instalados.
Esses plugins permanecem após uma reconstrução ou inicialização (bootstrap) de app ou web_only.
Atualmente, não foi testado em instâncias multisite e provavelmente falhará nesses cenários, pois o plugin precisa de acesso ao diretório /plugins do aplicativo para funcionar.
Os plugins instalados aparecerão em /admin/plugins.
Você PODE atualizar esses plugins normalmente em /admin/upgrade.
Durante o desenvolvimento deste plugin, identificamos um erro potencial ao remover traduções de plugins. Isso pode fazer com que o site exiba um erro se o usuário visitar uma página onde a tradução é usada. Isso parece ocorrer mesmo se você usar admin/upgrade para atualizar um plugin específico e o plugin tiver removido uma tradução. Estamos trabalhando para encontrar uma solução para isso no momento.
Requisitos:
Você deve estar executando uma instalação Docker suportada.
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.
Technically, it doesn’t matter. They end up being installed in exactly the same way. This just makes it easier to do.
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.
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.
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'
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.
