Score is an open source, platform-agnostic, container-based workload specification. This means you can define your workload once with the Score Specification and then use a Score Implementation CLI to translate it to multiple platforms, such as Helm, Docker Compose or Google Cloud Run.
In the example below, a score.yaml file is executed via score-compose to generate a compose.yaml file, which allows to spins up a container via Docker Compose. The same score.yaml file is then used to generate a helm values.yaml file to be installed onto Kubernetes.
Read the docs on how to install the Score implementation CLI.
The Score Specification file resolves configuration inconsistencies between environments. Compose a score.yaml file that describes how to run your Workload. As a platform-agnostic declaration file, score.yaml creates a single source of truth on Workload profiles and works to integrate with any platform or tooling.
# Generate compose.yaml with score-compose
score-compose run -f /tmp/score.yaml -o /tmp/compose.yaml
# Run the service with docker-compose
docker-compose -f /tmp/compose.yaml up backend
Cloud-native developers often struggle with configuration inconsistencies between environments. This gets even more complicated when the technology stack in each environment is different. What if you use Docker Compose for local development, but Helm Charts to deploy to the Kubernetes based development environment? Not only do you have to figure out Docker Compose and Helm, but you need to keep them in sync! This results in various bottlenecks along the application delivery lifecycle.
🎵 Tech & tools that require specialized knowledge and operational expertise are imposed on developers.
🎵 Different configuration rules, constructs and values between local and remote environments increase the risk of configuration inconsistencies.
🎵 Keeping a multitude of platform- and environment-specific configuration files in sync leads to repetitive configuration work.
Score provides a single, easy to understand specification for each workload that describes its runtime requirements in a declarative manner. The score.yaml file allows to generate configuration in an automated, standardized and one directional way. By reducing the risk of wrongly specified or inconsistent configuration between environments are we hoping to foster focus and joy for developers in their day-to-day work.
For more information, see Why Score.
- Give the project a star!
- Contact us via email:
- See our documentation.
- Write a blog.
- Provide feedback on our road map and releases board.
- Contribute.
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also open an issue with the tag enhancement.
- Fork the Project.
- Create your Feature Branch.
git checkout -b feature/feature-name - Commit your Changes.
git commit -s -m "Add some AmazingFeature" - Push to the Branch.
git push origin feature/feature-name - Open a Pull Request.
Read CONTRIBUTING for more information.
