Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Usage with monorepos #902

Open
gaui opened this issue Nov 25, 2018 · 0 comments
Open

Usage with monorepos #902

gaui opened this issue Nov 25, 2018 · 0 comments

Comments

@gaui
Copy link

gaui commented Nov 25, 2018

How would you use Draft with monorepos where all dependencies are managed at the root-level by some dependency manager like Paket / Lerna / etc.

Project structure might look something like this:

/
|-- .paket
|-- paket.dependencies
|-- Project_1
|   |-- API
|   |   |-- Dockerfile
|   |   `-- paket.references
|   |   `-- <project files>
|   `-- Client
|       `-- Dockerfile
|       `-- lerna.json
|   |   `-- <project files>
|-- Project_2
|   |-- API
|   |   |-- Dockerfile
|   |   `-- paket.references
|   |   `-- <project files>
|   `-- Client
|       `-- Dockerfile
|       `-- lerna.json
|   |   `-- <project files>

To be able to build the API in Project_2 I would need this build context:

/
|-- .paket
|-- paket.dependencies
|-- Project_2
|   |-- API
|   |   |-- Dockerfile
|   |   `-- paket.references
|   |   `-- <project files>

Is there some way to specify additional files with draft create command? What is the best way to achieve this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants