Since Score’s launch, we have received a lot of questions from the community about what it is, how it works, and who should use it. Here are our answers to the most frequently asked questions.
We are happy to announce that we reached 3000 stars on GitHub, with more than 300 people watching the repo and 1200 forks. Ad maiora!
In this article, we answer your questions about how Score compares to other tools in the space, specifically Kompose, HashiCorp Waypoint and Kubevela.
Score talks with the platform engineering community and introduces two of its main contributors and maintainers and goes deep diving on the reasons for its creation.
Most dev teams struggle with inconsistent configuration and a lack of transparency. Open source project Score tackles these problems.
We’re excited to announce that, together, we have reached a symbolic but meaningful milestone: 1K GitHub stars!
Score just received its 500th star on GitHub!
Score envisions a developer and workload-centric approach to improve developer productivity and experience. In this article, we take a deeper look at the “why” and see this as a starting point to discuss and shape a product vision we can work towards as a community.
Folks, we are extremely happy to announce that as of today, one week after launch, the Score project has already collected over 250 stars! Thank you!
In this tutorial you will learn how to get started with Score, a platform-agnostic, container-based workload specification. We will cover the creation of two Score Specification YAML files and how we can translate them to Helm values files and Docker Compose.
The Score Specification enables developers to run their workloads across different technology stacks without risking configuration inconsistencies. As a platform-agnostic declaration file, score.yaml presents the single source of truth on how to run a workload and works to utilise any container orchestration platform and tool - be it Docker Compose or Kubernetes.