Workspace support is being worked on, it was half-implemented before, so we are taking a proper pass at it now.
For switching between sessions, can you tell me about your workflow from before? Because a tab can hold a session from any project. Are you saying that opening up a tab is too heavy of an action?
GitHub issues though has been a problem from us, we deal with a ton of noise/spam.
I'm biased but for local development, I prefer to emulate the least amount of AWS services. You don't have to deal with any gotchas while going to prod.
Some background, with SST we connect your local environment to the services deployed to AWS and just run the Lambda functions locally: https://docs.sst.dev/live-lambda-development
Wow that antivirus warning on the docs is super weird. It's just a very simple docs site deployed through Netlify. Can you send me a screenshot of what you are seeing? I'll need to dig into it: [email protected]
Sorry to hear that you've had some bad experiences with SST. Recently we shipped some updates to fix the CPU issues with apps that have a large number of functions. The missing breakpoints I think is related as well.
That said though, we often work with teams in our Slack to get their setup working well. If you haven't, I'd recommend popping in and posting about it. Or just send me an email: [email protected] and we'll figure it out.
Yup it's meant to be a starting point for projects of all sizes. We built our own stuff using it as well. Feel free to reach out if you have any questions. Or join us on Slack: https://launchpass.com/serverless-stack
In this example, we show how to set breakpoints through VS Code and inspect a Lambda function. Let me know if you have any questions about how this works.
We had to change the build process of Lambdas to support deploying a mock version of the function. And we need to add a new command that deployed the debug stack.
Your existing CDK app should work with SST. The main difference is that SST deploys per stage (or environment). This allows you to do `sst start` that goes to one environment and `sst deploy --stage prod` that goes to another.
Ah I see what you are saying. Not that this approach is an anti-pattern compared to other serverless setups. But that serverless in general is an anti pattern.
I can see where you are coming from. What we are doing with SST does seem very complicated just to get a good local development setup.
Making it easy for startups to use serverless.
Comments and feedback welcome, [email protected]