From 99eaa001b682fb143f80875194e2e8ea3018a4b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Susa=20T=C3=BCnker?= Date: Thu, 27 Jun 2024 10:20:57 +0200 Subject: [PATCH] Updated link to demo code --- content/en/docs/overview/score-for-devs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/overview/score-for-devs.md b/content/en/docs/overview/score-for-devs.md index d72ea0bc..21a70919 100644 --- a/content/en/docs/overview/score-for-devs.md +++ b/content/en/docs/overview/score-for-devs.md @@ -11,7 +11,7 @@ Focus_Keyword: "Learn about Score as a developer" Score is a workload specification designed to simplify development for cloud-native developers. The spec enables you to describe your workload’s configuration in a vendor-neutral way, eliminating the need for tooling-specific syntax from platforms such as Docker or Kubernetes for example. By leveraging familiar concepts and semantics, defining a workload’s configuration becomes as simple as stating, "I want a database of type X and an event queue of type Y to accompany my workload". -Below you'll find an example of a simple Score application with a web server that queries a Postgres database on each request. The demo code can be found [here](https://github.com/score-spec/sample-app-gif). +Below you'll find an example of a simple Score application with a web server that queries a Postgres database on each request. The demo code can be found [here](https://github.com/score-spec/sample-app-gif/blob/main/score.yaml). ```yaml # The version string helps identify the Score file syntax