This is a great idea and I wish it success. Self-hosting shouldn't be a nightmare of researching and setting up 20 different applications.
Is there something similar in progress for a "tech company tech stack"? As in, rather than trying to assemble your own custom infrastructure by finding an RPC system, permissions/group manager, credential management, storage, database, service discovery, job management, monitoring etc. one "opinionated" stack that you can easily deploy, as long as you're OK accepting their choices, with all these parts already bundled and wired up.
Ruby/RoR doesn't really solve the e.g. monitoring problem, does it?
My goal is something that would work for startups that plan to grow beyond a single person/single server project. If you build the architecture for a too small size, you start running into walls as soon as you exceed that size.
But even if you are small, you probably want some kind of Grafana/Prometheus monitoring to tell you what's breaking. You want your framework pre-wired so it automatically reports data (e.g. requests/failures per service) without you having to set it up, because it it isn't automatic, you probably won't get around to setting it up until it's too late. You also want some kind of build system, CI/CD to handle deployment. An easy way to set up staging environments would be nice. If you don't want to use a hosted forge, then a self-hosted forge connected into all this.
My idea is to have one somewhat commonly adopted stack, where most of the stack "self-deploys" so you don't have to set up, connect, and coddle all of these services. If you want to deploy something within the stack, you're somewhat limited because you have to do it "the stack's way", but in exchange, once you've set it up, adding a staging environment consists of not actively disabling the default staging environment that the stack would set up for you otherwise, and once you've deployed your service, it's already pre-wired into your monitoring.
Popular packages would then over time likely get packaged for this stack, with service-specific monitoring exports (e.g. the postgres container could export query details rather than just the default-collected values like CPU usage and requests-through-the-standardized-RPC-framework).
Huh? Which of the things on that list are only needed at the billions of users scale? I'll give you "service discovery" and "dozens of services", sure, but everything else in there seems like a pretty standard need for a SaaS app that feeds a company of more than 10 people?
Is there something similar in progress for a "tech company tech stack"? As in, rather than trying to assemble your own custom infrastructure by finding an RPC system, permissions/group manager, credential management, storage, database, service discovery, job management, monitoring etc. one "opinionated" stack that you can easily deploy, as long as you're OK accepting their choices, with all these parts already bundled and wired up.