SYSTEM INFORMATION | |
---|---|
OS type and version | REQUIRED |
Webmin version | REQUIRED |
Virtualmin version | REQUIRED |
Webserver version | REQUIRED |
Related packages | SUGGESTED |
Please install n8n outbox
SYSTEM INFORMATION | |
---|---|
OS type and version | REQUIRED |
Webmin version | REQUIRED |
Virtualmin version | REQUIRED |
Webserver version | REQUIRED |
Related packages | SUGGESTED |
Please install n8n outbox
I don’t know what that is. The website (I assume you’re talking about this: https://n8n.io/) doesn’t make it very clear what use it would be in a web hosting environment.
Also, it’s not Open Source, and our policy is generally to only add Open Source apps to our web applications (there are a couple of exceptions, but there are good reasons for those exceptions). And, because it’s not Open Source, it’s not clear we’d even be legally able to provide tools to automate installation. We’d need to do some research and read their license carefully to know.
Hi Joe,
N8N is open source. I think a lot of people wanted it because it’s a very good automation tools. You only need nodejs (optionally with postgres) to run it.
I don’t know how virtualmin templates works, but I do know the steps to install it using terminal: recipes/boot/n8n.yml at master · domcloud/recipes · GitHub
Not Open Source. n8n/LICENSE.md at master · n8n-io/n8n · GitHub
To be clear: Source-available does not mean it is not proprietary software. That is a proprietary software license. Which is fine, we distribute Virtualmin Pro under a non-Open Source license, I’m not arguing about how they should license their software. But, we have very good reasons for not wanting to get mixed up with distributing/interacting with proprietary software.
That’s an interesting idea—n8n outbox could definitely bring some cool automation to Virtualmin. Hope the team considers it!
As I’ve mentioned, it is not Open Source, so it is very unlikely to ever be directly supported in Virtualmin.
But, nothing is stopping you from using it on the same system that runs Virtualmin. It’s just a Node JS app also available in a Docker container, so you just proxy to it as you would any other apps running on Docker or under an app server.
Got it, thanks! I’ll try running it alongside Virtualmin and set up a proxy—it’s helpful to know it’s doable that way.