[Feature Request] UI Plugin Support

[aiminickwong]

I suggest add a UI plugin support, people can add their UI files by them self, don't need to compile to program, example with used "docker -v outside_directory:container_directory" to add their ui plugin files.

For example:
In Defined UI Plugin path directory we add some files like this:

---

____module.js : /* plugin custom defined file*/

/* left sidebar name(title) , Uniform format sample requirements . */

/* define panel title and entrance index html file */

/* Permissions: users or team that who can be accessed */

---

views : --/* directory */
|_______ index.html --/* right area index page, user's custom index html file */
|___ js:
|_____ example.js -- /* user's custom js */
|___ page :
|_____ example.html --/* user's custom js */
|_____ example2.html --/* user's custom js */

---

So, with this everyone can add plugins by them self, let this project become more open and powerful and let more people participate in this project, with the plugin support we can do more much things what we want.

@ncresswell @deviantony

[deviantony]

We're going to add Plug-in support into Portainer, we still need to decide if we want to make this model "open" so that users can actually create their own plugins.

[ncresswell]

We should support community created plugins for sure Rgds, Neil Cresswell On 21/06/2018, at 6:53 PM, Anthony Lapenna <notifications@github.com<mailto:notifications@github.com>> wrote: We're going to add Plug-in support into Portainer, we still need to decide if we want to make this model "open" so that users can actually create their own plugins. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_1932-23issuecomment-2D398995684&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=2Ez-MobJV8pqAst9F4t5ITzK_NNnGHllStWotSsNveU&s=GPAxLM_rJfTnDM0pwGPZJ_sCnhKvcgpmv0dFSbe4SBw&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlTBKm-2D35XRy1CGJ3dUsTTGNDrNI8ks5t-2D0LdgaJpZM4UNlcW&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=2Ez-MobJV8pqAst9F4t5ITzK_NNnGHllStWotSsNveU&s=bE7mxAiMkCmxJeP2ENTFWt0YjAmgOWqJziRTIM4wWFs&e=>.

[olljanat]

@aiminickwong I'm just curious that which kind plugins you have in mind?

As there is multiple ways to get similar results. For all generic stuff pull requests are of course best option so everyone will get them to use. Customizations can be also build outside of Portainer and make them just communicate over API.

What is best method of course depends on use case.

[aiminickwong]

@olljanat some monitors and service discovery, Load balancing proxy, etc.

[github-actions]

This issue has been marked as stale as it has not had recent activity, it will be closed if no further activity occurs in the next 7 days. If you believe that it has been incorrectly labelled as stale, leave a comment and the label will be removed.

[github-actions]

Since no further activity has appeared on this issue it will be closed. If you believe that it has been incorrectly closed, leave a comment mentioning portainer/support and one of our staff will then review the issue. Note - If it is an old bug report, make sure that it is reproduceable in the latest version of Portainer as it may have already been fixed.

[blank-software]

I am also interested in a plugin system for customizing Portainer. I want to be able to tweak the UI, add buttons here and there, and maybe some custom javascript.

My use case is as follows: we use Portainer in my team to create personal development containers where each developer can install their IDE and start coding. I want to create something like "wizard" experience for creating a new container. I know there are app templates and we already use them, but I need more flexibility.

Each container needs to have a strong SSH password set as an environment variable (I would prefer this to be randomly-generated, the user can find it later on the container details page), certain volumes mapped depending on the user creating it and ports assigned based on a custom rule. Each container should also follow a specific naming convention that we have.

Right now, each user needs to expand the Advanced settings and set these parameters by hand. We have internal instructions for everything, but it's still needlessly complicated.