Questo plugin è progettato per rendere estremamente semplice l’installazione di nuovi plugin senza dover accedere al server. Aggiunge una schermata disponibile in /admin/plugins/procourse-installer che appare così:
Da lì, puoi inserire l’URL (con o senza .git) del repository Git del plugin e fare clic su Installa Plugin. Attendi qualche minuto (circa 5 minuti) il completamento dell’installazione e sarai pronto per iniziare.
Per visualizzare tutti i plugin installati tramite l’installer o per rimuovere un plugin, vai semplicemente su Plugin Installati.
Questi plugin rimangono anche dopo una ricostruzione o un’avvio iniziale (bootstrap) di app o web_only.
Al momento non è stato testato su istanze multisito e probabilmente fallirà in tali scenari, poiché il plugin necessita di accesso alla directory /plugins dell’applicazione per funzionare.
I plugin installati appariranno sotto /admin/plugins.
Puoi aggiornare questi plugin normalmente da /admin/upgrade.
Durante lo sviluppo di questo plugin, abbiamo rilevato un potenziale errore durante la rimozione delle traduzioni dai plugin. Ciò può causare la visualizzazione di un errore sul sito se un utente visita una pagina in cui viene utilizzata la traduzione. Questo sembra accadere anche se si utilizza admin/upgrade per aggiornare un plugin specifico e il plugin ha rimosso una traduzione. Stiamo attualmente lavorando per trovare una soluzione.
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.
