#Hey! I have a module checked out locally

1 messages · Page 1 of 1 (latest)

pseudo zodiac
#

It looks like that's in a separate git repo locally? I believe the "parent context directory" refers to the git repo your module is in and a local dependency must be in that same git repo

upbeat pendant
#

hmm

#

can't I have 2 repos checked out and then do "dagger install" and install something from source?

#

PS: Hey Kyle 👋

#

How would you do this? what's your local development workflow, when you're building a module locally, and wanna test it on one of your apps

mystic shoal
#

At the moment Dagger lacks an equivalent of Go's "replace" directive, where you can replace any remote dependency with a local checkout of it, regardless of which repos they are in.

pseudo zodiac
#

I wonder if a symlink could work like replace?

upbeat pendant
#

so how would you do it @mystic shoal

Obviously I want to avoid the Push and Pray (the irony)

mystic shoal
#

At the moment you have to either 1) co-locate the modules you're co-developing in the same repo; 2) vendor one in the repo of the other; 3) push one module to a dev branch, so you can remotely import it from the other

upbeat pendant
#

co-locate .. so you mean I make a "sub-dierctory" on my current git repo, and invoke it there?

# 
dagger install ./my-dagger-module

?

#

or do you mean side by side

../my-dagger-module
#

@mystic shoal

#

okay, the first one worked .. the second one didn't work

#

is that what you meant?

upbeat pendant
#

all issues resolved.