daggerverse/slim-with-docker at main · s...

[fresh python]

The reason I renamed it to slim-with-docker is to make it possible to have a native slim module that doesn't have the docker dependencies; might be better to combine them into one module eventually. What do you think? What's the official Dagger recommended way? @urban condor @compact lodge @stiff steeple

[compact lodge]

This is my subjective opinion since we don't have an official policy: I would make it a single slim module, where you can either change the underlying implementation of functions (to remove the dockerd dependency for example), or add more choice of functions, eg. one with dockerd and one without. I think having one module with a simple name makes it easier to find your module, and removes friction (don't need to think about which one to use etc)

[fresh python]

Good points!! I didn't want to break the docker-based version while i'm working on the native version, but it should be easy to have a 'mode' flag to switch between docker and dockerless version.