porting existing python codebase to windmill #5662
-
I have an existing (non-trivial, but not terribly complicated) python codebase that I'd like to try "porting" to run on Windmill, and I'm trying to understand the best approach for this. This codebase already has some of its own modules (and thus eg imports of local modules). As a simple representative example, suppose...
Based on my reading of docs etc so far, the "Windmill-y" way to port this (let's call this Option A) would be to move/rename modules to fit into Windmill's Another option I see for "porting" this (let's call it Option B) is to just build a container image and run this in windmill that way. This would not require many/any code changes, but would obviously not allow us to take advantage of as many of the cool features of the windmill platform. Am I missing any potential options here, or am I misunderstanding either of the options? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I would recommend exploring building your codebase as a wheel that you publish to a registry, maybe pypi and using it in Windmill as a normal library import. For typescript we have bundles but there are no canonical way to do bundles in python so we do not support. But otherwise, yes A is the better one if you can do it. You can use any nesting level so the f/... restriction is not a big one. |
Beta Was this translation helpful? Give feedback.
I would recommend exploring building your codebase as a wheel that you publish to a registry, maybe pypi and using it in Windmill as a normal library import.
For typescript we have bundles but there are no canonical way to do bundles in python so we do not support.
But otherwise, yes A is the better one if you can do it. You can use any nesting level so the f/... restriction is not a big one.