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

if you're using the same state yeah. Generally you'd login to the same state backend, and then name your project something like
`&lt;project&gt;.&lt;envrionment&gt; - so vpc.producton

You can then reference your stack in a similar way to the <http://app.pulumi.com|app.pulumi.com> backend

Hmm. I infer from that that I've been using backend urls incorrectly... I'm logged into <http://app.pulumi.com|app.pulumi.com>, and my Pulumi.yaml files all include bits like this:
```backend:
  url: <s3://mypulumibucket/pulumi/thisproject>```
So there's no relationship between projects via the login, it's all done via a common s3 bucket....

To get what I want, I would have to use one file in my bucket for all project states:
```backend:
  url: <s3://mypulumibucket/pulumi>```
Which would mean I'd need stricter locking. But Pulumi can handle multiple projects and stacks in a single state file, so long as the locking is handled for it.
I think I'll wait until we move to <http://app.pulumi.com|app.pulumi.com> (or self-hosted) before doing that. Which means waiting until it's more entrenched here so that no one tells me to stop using it and to go back to Terraform :wink: