Jay
Then run it async, publish it to a Topic and handle those events. Here's a simple example: https://sst.dev/examples/how-to-use-pub-sub-in-your-serverless-app.html
I'll check on the `--path` option but we don't recommend this setup. The config needs to be at the root, is there a reason why it's in a sub directory?
The way to think about this is that SST is packaging and deploying both the frontend and the API. So it'll be odd if they are sitting side by side....
Yeah we used to have it in SST v1 when things were structured a little differently. We need to remove it from the docs.
Good point! @fwang can we add this to the Migration guide?
Usually it's just moving the `sst.config.ts` to the root. What does your project structure look like?
What's the issue? We don't have the env command anymore.
I'm kinda confused by what you are saying? Can you post your project structure in #help on Discord? We'll take a look.
Let me ask Dax to take a look and then can you submit a PR with this @moochannel?