To me, it looks like this new project is aimed more at being able to develop remotely and share your localhost:3000 env instead of getting a real production box up. Bidi sync etc... hints at that, it's like having a 2-interface dev env.

I don't see that at all?

The network effect gets compounded by LLMs/vibecoding. I'm not just talking about v0 or replit either. Fire a prompt at ChatGPT to build a web app and most of the time it will give you react components in return.

Makes sense to me. I've read that LLMs are more competent in React than other frameworks.

Even if you tell it not to use React?

No, but think about the trajectory. Most people new to building a frontend bare-prompt. There's value for them in using the most supported language, including support from AI systems.

Can someone please make a zyn tin container for these?

Hi! Sorry it took a bit, had to redact some information off the screenshots. The dashboards can be assembled out of components that show specific information, so there's no singular dashboard. Instead, you can use the components to make a screen that has a bunch of information that's relevant to your everyday workflow.

We do have some sample dashboards here, what we think would be useful for AWS Account level settings, ECS services, SQS queues, and general markdown to describe a runbook or - https://github.com/tinystacks/opsconsole/tree/main/samples. I'm also pushing up images for each sample.

I recommend taking a look at the ECS sample because that gives a taste of how far these dashboards can go. https://github.com/tinystacks/opsconsole/blob/main/samples/e...

tl;dr, screenshot's here: https://github.com/tinystacks/opsconsole/blob/main/samples/e...

It can be made to! It needs a plugin for that, the default plugins don't support that.

We don't have an ETA there yet. I opened issues for GCP support, please +1 them to help us prioritize! https://github.com/tinystacks/precloud/issues

Good idea. I recommend running it in your ci cd provider as a post-build stage (I.e. reference it in your github/gitlab workflow on each pull request)

Done!

Hey Cube! It does indeed run checks against the cloud as well for things like naming collisions and quota allocation

Could you expand on how you're doing that, technically? I'm really curious and can't find it in the code, skimming it quickly.

Yeah, so this package itself is the core framework that establishes how these tests are to be run. There is a notion of plug-ins, which are parsers and checks. Parsers take cdk or terraform code and break their synthesized/planned output out into a common structure. Then checks run over that structure and pull data in from elsewhere and run actual validations. You can read more in the developing plugins doc on the repo https://github.com/tinystacks/precloud/blob/main/DEVELOPING_....

The default plugins present are the 6 mentioned here https://github.com/tinystacks/precloud/blob/main/PLUGINS.md. They’re all published on npm and github

Oh, that's cool, thanks for the explanation!