Este plugin está diseñado para hacer extremadamente fácil la instalación de nuevos plugins sin necesidad de iniciar sesión en el servidor. Agrega una pantalla en /admin/plugins/procourse-installer que se ve así:
Desde allí, puedes ingresar la URL (con o sin .git) del repositorio git del plugin y hacer clic en Instalar Plugin. Espera unos minutos (aproximadamente 5 minutos) a que se complete la instalación y ya estarás listo.
Para ver todos los plugins que has instalado a través del instalador o para eliminar un plugin, simplemente ve a Plugins Instalados.
Estos plugins SÍ permanecen después de una reconstrucción o arranque (bootstrap) de app o web_only.
Actualmente no se ha probado en instancias multisitio y probablemente fallará en esos escenarios, ya que el plugin necesita acceso al directorio /plugins de la aplicación para funcionar.
Los plugins instalados SÍ aparecerán en /admin/plugins.
SÍ puedes actualizar estos plugins de forma normal desde /admin/upgrade.
Durante el desarrollo de esto, encontramos un error potencial al eliminar traducciones de los plugins. Esto puede hacer que el sitio muestre un error si el usuario visita una página donde se utiliza la traducción. Esto parece ocurrir incluso si usas admin/upgrade para actualizar un plugin específico y ese plugin ha eliminado una traducción. Estamos trabajando actualmente en encontrar una solución para esto.
Requisitos:
Debes estar ejecutando una instalación de Docker compatible.
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.
