Have you seen this?
do not work for OMV5 & portainer 2.x
for me only works: https://raw.githubusercontent.…master/templates-2.0.json
https://raw.githubusercontent.…V5/Template/template.json
works fine for portainer 1.x
Have you seen this?
do not work for OMV5 & portainer 2.x
for me only works: https://raw.githubusercontent.…master/templates-2.0.json
https://raw.githubusercontent.…V5/Template/template.json
works fine for portainer 1.x
That would be difficult to implement in a plugin since there needs to be a combo of javascript and php code. I don't know of a way to populate web interace objects from a yaml (or anything else) file. A normal plugin is almost what you are describing. Maybe that will be easier with OMV 6.x.
Here's a (probably crazy) thought...
1. Create a plugin that, instead of installing some service, builds a specific docker container and puts a config file in the right place so the container can see it. The config file would be built from a template by replacing some fields with values from the plugin's panel, such as a shared folder selected from a dropdown, just like a regular plugin. Changes to the plugin's configuration would result in the container being rebuilt and a new config file being placed in the container's folder.
2. (This is the hard part) Write a script that does step 1 for you, taking input from some kind of settings file. You can use this script to make many different docker-based plugins. The fields available in the generated plugin's panel are described in and generated from the settings file.
3. Create a plugin that accepts a settings file and runs the script from step 2. The settings file can by typed/pasted in, uploaded from a local file, or pulled from a URL. Power users can publish their settings files as a URL or file that can be pasted into this plugin to create a new docker-based plugin.
do not work for OMV5 & portainer 2.x
from here: https://github.com/SelfhostedPro/selfhosted_templates
Zitatportainer 2.0 templates are available here in the portainer 2.0 branch. The Template URL is
https://raw.githubusercontent.com/SelfhostedPro/selfhosted_templates/portainer-2.0/Template/template.json
.
Here's a (probably crazy) thought...
1. Create a plugin that, instead of installing some service, builds a specific docker container and puts a config file in the right place so the container can see it. The config file would be built from a template by replacing some fields with values from the plugin's panel, such as a shared folder selected from a dropdown, just like a regular plugin. Changes to the plugin's configuration would result in the container being rebuilt and a new config file being placed in the container's folder.
2. (This is the hard part) Write a script that does step 1 for you, taking input from some kind of settings file. You can use this script to make many different docker-based plugins. The fields available in the generated plugin's panel are described in and generated from the settings file.
3. Create a plugin that accepts a settings file and runs the script from step 2. The settings file can by typed/pasted in, uploaded from a local file, or pulled from a URL. Power users can publish their settings files as a URL or file that can be pasted into this plugin to create a new docker-based plugin.
It isn't completely crazy. Just not sure how flexible I could make it. I will look into it a little bit.
still not works on create custom template.
do you try it?.
please guide me ( open a new thread if is apropiate).
Alles anzeigenstill not works on create custom template.
do you try it?.
please guide me ( open a new thread if is apropiate).
Try using Yacht and the Yacht template instead. You can set template variables so things like !config go to /sharedfolders/AppData/config or wherever you want.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!