No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

-.txt

Ours is structured:
```
- components
  - aws-dns-root-zone
  - aws-network
  - aws-postgresql
  - azure-rbms
  - [etc.]
- services
  - gitlab
  - gitlab-runner
  - jira
  - [etc.]
- environments [for singletons, like our infra env that hosts gitlab etc.]
  - infra
- deployables
  - app [which is deployed to prod, preprod, qa1, qa2, dev-foobar, etc.]
```

They all live in a single Yarn workspace.

yeah, but if I understand correcty the different environment are not separated, right? I mean just on the stack level

Environments that are singular are separated.

If it's actually  a per-deployment _stack_, then no.

what do you mean by singular? where do you have the pulumi specific configs like Pulumi.yaml?

I tried to put those to the env specific dirs(dev,prod), but then it's unable to find the modules from "node_modules" when running "pulumi up"

When I mean singular, I mean exactly that - we have one "infra" env because it's where gitlab, jira, etc. live. Their stack _state_ is commingled in with the others.

and you have env specific condition(like if-s) in "infra"?

We just have exactly one of them, so it gets its own entry-point file.

so you just run "pulumi up" from the infra directory, right?