Nyno is an open-source multi-language workflow engine and language that lets you build, extend, and connect automation in the languages you already know — Python, PHP, JavaScript, and Ruby.
Each programming language runs in its own high-performance worker engine. Command-steps can be called in human-readable YAML Workflows (.nyno files).
feedback: i'm trying to understand the highlevel flow/usage but still a bit confused.
ideas:
1) maybe add a .yml example to the readme under the /test_nyno screenshot so i know how you configured that workflow
2) what are ways to trigger a workflow? just tcp?
3) the example runs "bestjsserver" which looks like it runs workflows? are some workflows auto running? that just logs from tcp commands you manually running in other terminal? a bit confused what's going on here
3) Workflows in the workflow-enabled folder are automatically loaded and available, so you can execute those workflows via the drivers (ex. for Python, JavaScript, PHP projects).
You can both execute dynamic workflows (like executing a scripting language) or put .nyno files (YAML) in the workflow-enabled folder, so you can run the workflow using the runWorkflow() functions specified in the drivers.
It's source is available, but n8n is not open-source. They have restrictions if you don't use their cloud service for non-internal tools (ex. commercial public API's): https://docs.n8n.io/sustainable-use-license/
theyogadev|3 months ago
Each programming language runs in its own high-performance worker engine. Command-steps can be called in human-readable YAML Workflows (.nyno files).
tomhallett|3 months ago
ideas:
1) maybe add a .yml example to the readme under the /test_nyno screenshot so i know how you configured that workflow
2) what are ways to trigger a workflow? just tcp?
3) the example runs "bestjsserver" which looks like it runs workflows? are some workflows auto running? that just logs from tcp commands you manually running in other terminal? a bit confused what's going on here
Thanks!
theyogadev|3 months ago
1) Yes, I will add an examples folder.
2) 100% TCP, yes. You can also send YAML directly to it, using it like a command, ex. https://github.com/empowerd-cms/nyno-lang
3) Workflows in the workflow-enabled folder are automatically loaded and available, so you can execute those workflows via the drivers (ex. for Python, JavaScript, PHP projects).
You can both execute dynamic workflows (like executing a scripting language) or put .nyno files (YAML) in the workflow-enabled folder, so you can run the workflow using the runWorkflow() functions specified in the drivers.
Easiest way to quickly test is to execute .nyno files directly via https://github.com/empowerd-cms/nyno-lang
(PS. the bestjsserver is what powers the GUI + TCP setup, but the steps of each workflows are run in seperate workers engines for each language)
ariejan|3 months ago
How is this at version 3.0 in just two months?
theyogadev|3 months ago
In version 2 we used JSON + YAML, now we use just YAML everywhere.
TZubiri|3 months ago
theyogadev|3 months ago
popalchemist|3 months ago
theyogadev|3 months ago
unknown|3 months ago
[deleted]