jmr
Updating the app UI from within a running script
Is there a way to broadcast information from within a running script that I could propagate to the UI?
I have a single script that triggers another system, via subprocesses, and waits for the other system to complete. That system on startup prints a link for the status page of that system to stdout. I'd like to propagate that link to the UI, before the subprocess is finished and the script is done.
I can currently see it in the logs element of the app, but it would be nice if I could extract that out separately so users don't have to search around for it in the logs.
1 replies
Questions around licensing
I've got a few questions around use of AGPL as well as enterprise licensing.
1. AGPL suggests that software must be kept open source if changed. I assume I am ok to use it in a commercial setting as long as I don't modify the software, and it stays internal to the company. I assume things that I run via windmill do not get tainted with AGPL, (nor does building a docker image on top of windmill image adding company CA certs).
2. We have a secondary company that provides operational support for us (eyes on glass, 24hr on call), as we don't run that ourselves. We provide the scripts, they make sure they run, rerun in case of failures etc. Is it in breach of the open-source license if we expose windmill scripts to the support company? All the support people would be operators only.
3. My idea to use windmill doesn't really fit in with where windmill positions itself. Namely I am mostly looking for a ui for running and configuring parameterizable cron jobs that can be kicked off ad-hoc (script does some argument validation). The scripts that we'd run via windmill would just do a submission to our internal compute farm, and windmill would mostly sit there in a loop polling for that to complete. The submission starts a process that needs to stay alive (bring back logs, process disappearing suggests cancellation etc), so I can't move the "waiting for it to complete" into some sort of flow loop that reduces the execution time (from windmills perspective). This in nature makes the enterprise license not really viable, as we'd be paying quite a lot for windmill just to sit and sleep in a loop. These jobs that we submit to our compute farm can run for 2-3 days so we'd have scripts that would run for this long in a single script execution. Perhaps windmill is not the right product for us, atleast when it comes to enterprise license?
3 replies