Skip to content

Commit

Permalink
add workspace tool links
Browse files Browse the repository at this point in the history
  • Loading branch information
theoephraim committed Nov 22, 2024
1 parent b2bf26c commit 1fd361c
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions packages/docs-site/src/content/docs/docs/guides/monorepos.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@ By default, DMNO will rely on your existing tooling to detect where potential ch

| Workspace tool | Globs location |
|---|---|
| npm, yarn, bun | `package.json`<br/>└ `workspaces` |
| pnpm | `pnpm-workspace.yaml`<br/>└ `packages` |
| moonrepo | `.moon/workspace.yml`<br/>└ `projects` |
| [npm](https://docs.npmjs.com/cli/v8/using-npm/workspaces), [yarn](https://yarnpkg.com/features/workspaces#how-are-workspaces-declared), [bun](https://bun.sh/docs/install/workspaces) | `package.json`<br/>└ `workspaces` |
| [pnpm](https://pnpm.io/workspaces) | `pnpm-workspace.yaml`<br/>└ `packages` |
| [moonrepo](https://moonrepo.dev/docs/config/workspace#projects) | `.moon/workspace.yml`<br/>└ `projects` |

In some situations, like in a large polyglot repo, or a large repo that has multiple smaller monorepos within it, you may need an alternate way of defining where to look for DMNO services. In this case, you can create a `workspace.yaml` in your workspace root's `.dmno` folder. If this file is found, it will override everything else.

Expand All @@ -57,7 +57,7 @@ To solve this, [`dmno run`](/docs/reference/cli/run/) boots up a server that oth
:::tip[Env var pass-through]
We use an injected `DMNO_PARENT_SERVER` env var to detect the parent server, so it must be passed through to child processes.

In [turborepo "strict mode"](https://turbo.build/repo/docs/crafting-your-repository/using-environment-variables#strict-mode), env vars are not all passed through by default. We must explicitly tell turbo about it using the [`globalPassThroughEnv`](https://turbo.build/repo/docs/reference/configuration#globalpassthroughenv) setting. For example:
In [Turborepo "strict mode"](https://turbo.build/repo/docs/crafting-your-repository/using-environment-variables#strict-mode), env vars are not all passed through by default. We must explicitly tell turbo about it using the [`globalPassThroughEnv`](https://turbo.build/repo/docs/reference/configuration#globalpassthroughenv) setting. For example:

```diff lang=json title='turbo.json'
{
Expand Down

0 comments on commit 1fd361c

Please sign in to comment.