saltyorg
Automate Additional Portainer Environment
Describe the problem When running multiple instances (Mediabox & Feederbox). Utilise the same instance of portioner instead of having multiple instances running on each version. Portainer is designed to handle multiple environments so having an automated way of implementing an environment for instance MediaBox & Feederbox in 1 dashboard will ease visibility
Describe any solutions you think might work So adding an environment is reasonably easy. (Add A Docker Standandalone Environment) It's how would this be integrated within the Saltbox Ecosystem.
Additional context I have a production and development environment running both saltbox. AS can be seen in the image
This could be named as Mediabox & Feedbox or the type of role that's been installed
Portainer setup is manual and already allows this.
On Tue, Feb 25, 2025, 12:40 Barrow1990 @.***> wrote:
Describe the problem When running multiple instances (Mediabox & Feederbox). Utilise the same instance of portioner instead of having multiple instances running on each version. Portainer is designed to handle multiple environments so having an automated way of implementing an environment for instance MediaBox & Feederbox in 1 dashboard will ease visibility
Describe any solutions you think might work So adding an environment is reasonably easy. (Add A Docker Standandalone Environment https://docs.portainer.io/admin/environments/add/docker) It's how would this be integrated within the Saltbox Ecosystem.
Additional context I have a production and development environment running both saltbox. AS can be seen in the image image.png (view on web) https://github.com/user-attachments/assets/a2021d51-3727-47d6-b4a6-e49feed271a6
This could be named as Mediabox & Feedbox or the type of role that's been installed
— Reply to this email directly, view it on GitHub https://github.com/saltyorg/Saltbox/issues/316, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSIMLXXMBFUDR6JC5WPZVD2RRJDXAVCNFSM6AAAAABX2NH64WVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3TQMJRGIYTMMY . You are receiving this because you are subscribed to this thread.Message ID: @.***> [image: Barrow1990]Barrow1990 created an issue (saltyorg/Saltbox#316) https://github.com/saltyorg/Saltbox/issues/316
Describe the problem When running multiple instances (Mediabox & Feederbox). Utilise the same instance of portioner instead of having multiple instances running on each version. Portainer is designed to handle multiple environments so having an automated way of implementing an environment for instance MediaBox & Feederbox in 1 dashboard will ease visibility
Describe any solutions you think might work So adding an environment is reasonably easy. (Add A Docker Standandalone Environment https://docs.portainer.io/admin/environments/add/docker) It's how would this be integrated within the Saltbox Ecosystem.
Additional context I have a production and development environment running both saltbox. AS can be seen in the image image.png (view on web) https://github.com/user-attachments/assets/a2021d51-3727-47d6-b4a6-e49feed271a6
This could be named as Mediabox & Feedbox or the type of role that's been installed
— Reply to this email directly, view it on GitHub https://github.com/saltyorg/Saltbox/issues/316, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSIMLXXMBFUDR6JC5WPZVD2RRJDXAVCNFSM6AAAAABX2NH64WVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3TQMJRGIYTMMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
An inventory toggle to deploy the agent instead of full Portainer could make sense. I believe it will require a port bind and cannot be reverse proxied and the setup within Portainer would need to be done manually.
An inventory toggle to deploy the agent instead of full Portainer could make sense. I believe it will require a port bind and cannot be reverse proxied and the setup within Portainer would need to be done manually.
Which would be the best implementation? I feel they may be security implications if leaving it wide open without authentication
Ah yes the basic agent implementation does not have auth (why, Portainer, why) so perhaps the Edge Agent which does not require a port bind and calls from the agent host to the primary Portainer instance with an API key would be a better approach.
Personally, I use the standard Agent implementation bound to Tailscale only.
@owine you want to do this in the role-refactor branch now or are we closing this?
No we should close this. Deploying the edge agent isnt something we can easily automate. Portainer will generate the docker syntax anyway to speed deployment