Launched a new project to ensure consistent config across environments. 🚀 Feedback appreciated!

Any devs struggling with config inconsistencies between environments? Like, if you use Docker Compose for local dev but Helm Charts to deploy to the K8s-based dev environment, you have to figure out both tools AND keep them synced up. In addition to being a PITA for individual devs, in my experience, it also seems to create a lot of bottlenecks in the delivery cycle.

I’m working on an open source project called Score to tackle this problem. What are your thoughts on our take?

Here's what we did:

• Establish a single source of truth for workload config → We can generate one directional config and combine it with env-specific parameters in the target env.
• Shield developers from config complexity (think container orchestrations and tooling) with a well-scoped workload spec.
• Use a declarative approach for infra management so that devs can describe a workload’s resource dependencies without having to worry about the details in the target env.

I welcome all feedback! And thanks in advance!