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!
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)
How is this at version 3.0 in just two months?
In version 2 we used JSON + YAML, now we use just YAML everywhere.
theyogadev•2mo ago
Each programming language runs in its own high-performance worker engine. Command-steps can be called in human-readable YAML Workflows (.nyno files).