#Installing another module from the local filesystem outside of a git repo

1 messages · Page 1 of 1 (latest)

quiet urchin
#

Hi there, I'm trying to understand what my options are for referencing another module I've created on the local filesystem, rather than from a remote repo. I currently have 2 sibling directories module1 and module2. If my understanding and experimentation is correct, module1 can install module2 as a dependency (i.e. dagger install ../module2 if they both exist within a git repo, but if they are outside a git repo I'll be hit with an "escapes context" error. Do I have any control over the context? i.e. can I set the context to be the parent directory myself via the cli?

Just to add a bit more info on what I'm trying to do - I'm experimenting with bundling these modules inside a dotnet tool which acts as a very thin wrapper over the dagger cli. This essentially means that when someone installs the tool, the modules will exist on the filesystem, but in the tool install directory rather than inside a git repository. This means any dependencies I have created between my modules breaks.

Any info would be greatly appreciated!

undone niche
#

Thanks for the details on your use case, I don't completely understand what the lifecycle of the modules would be though..

kind lynx
quiet urchin
#

Yep that's correct. We have a single repo where we develop and test the modules. From there they can be consumed as required, possibly as remote modules. For the use case I was testing I wanted to bundle them into the tool so consumers of the tool didn't need access (and authorisation) to the module repo. I realise there are some downsides to this e.g. having to publish a new version of the tool if any of the modules change, but it's an approach that hopefully makes things simpler for consumers. I'll just stick to remote modules for now. Thanks for the reply!

undone niche