#dagger init

1 messages · Page 1 of 1 (latest)

hollow hound
#

I'm thinking maybe dagger init could be made to no longer need the engine at all? @pure vigil

#

Just a super lightweight git init-like

#

and dagger develop does the heavy lifting

pure vigil
#

could do, not sure why it needs it at the moment. it did create the dagger.json for me at least before I interrupted it

#

in general we've been trending towards pushing more dagger.json related things engine side though

#

for example i'm doing that now for the module loading flow, so that we can have all the internal stuff tucked away under a single init(ref: ".") API call instead of scattered around the toplevel

#

if we can easily do it as a lightweight git init thing though, seems like we still should, if not just to have fewer moving parts involved w/ bootstrapping

#

this was slightly terrifying, considering at one point Directory.export used to nuke the destination dir 😅

❯ dagger develop --sdk go
∅ Directory.export(path: "/home/vito"): Boolean! 9.2s
  ✔ export directory / to host /home/vito 9.2s