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

hi catriel! i have a very similar setup for my own homelab :slightly_smiling_face: (micro stacks, but no NX yet)

&gt; I needed create an organization for this project so I can group the all micro-stacks under the same parent so the `StackReference` make sense.
i’m curious what you mean by this. in my case, i have a stack like `parent/env`  for my cluster, and the children `app1/env`, `app2/env`, etc. each have a reference to `parent/env`. so at least in my case the org-level grouping wasn’t needed, although i could understand why it would be helpful (especially if you have other non-homelab stacks in your account)

Hi <@U03MCHZARD0>.  I glad to hear that I'm not the only one that uses Pulumi for local environments :grin:.
Yes, I have another projects on my account and I want keep this isolated because I don't wanna mess the structure adding prefix on every project like `homelab_postgresql` and also there is no way to limit which projects can make a stack reference.

image.png

re: keeping things isolated, you can add a stack tag to your homelab things. then in UI’s stack list there’s a “group by” menu in the upper left that can help you group those things together.