diff --git a/blog/2023-07-14-kcl-0.5.0-release/index.md b/blog/2023-07-14-kcl-0.5.0-release/index.md index 7f8395a1..bbc84382 100644 --- a/blog/2023-07-14-kcl-0.5.0-release/index.md +++ b/blog/2023-07-14-kcl-0.5.0-release/index.md @@ -406,8 +406,8 @@ spec: params: name: app containers: - ngnix: - image: ngnix + nginx: + image: nginx ports: - containerPort: 80 service: diff --git a/blog/2023-09-08-dcm-using-kcl/index.md b/blog/2023-09-08-dcm-using-kcl/index.md index d3598c67..ce79afe8 100644 --- a/blog/2023-09-08-dcm-using-kcl/index.md +++ b/blog/2023-09-08-dcm-using-kcl/index.md @@ -108,8 +108,8 @@ spec: params: name: app containers: - ngnix: - image: ngnix + nginx: + image: nginx ports: - containerPort: 80 service: diff --git a/docs/user_docs/concepts/type-and-definition.md b/docs/user_docs/concepts/type-and-definition.md index 0801b746..ed82315f 100644 --- a/docs/user_docs/concepts/type-and-definition.md +++ b/docs/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/docs/user_docs/guides/abstraction.md b/docs/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/docs/user_docs/guides/abstraction.md +++ b/docs/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/examples/abstraction/main.k b/examples/abstraction/main.k index 00fc349c..48a0697b 100644 --- a/examples/abstraction/main.k +++ b/examples/abstraction/main.k @@ -2,8 +2,8 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/2023-07-14-kcl-0.5.0-release/index.md b/i18n/zh-CN/docusaurus-plugin-content-blog/2023-07-14-kcl-0.5.0-release/index.md index ae17a93c..e0649b49 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-blog/2023-07-14-kcl-0.5.0-release/index.md +++ b/i18n/zh-CN/docusaurus-plugin-content-blog/2023-07-14-kcl-0.5.0-release/index.md @@ -408,8 +408,8 @@ spec: params: name: app containers: - ngnix: - image: ngnix + nginx: + image: nginx ports: - containerPort: 80 service: diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/2023-09-08-dcm-using-kcl/index.md b/i18n/zh-CN/docusaurus-plugin-content-blog/2023-09-08-dcm-using-kcl/index.md index 82916de1..43871beb 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-blog/2023-09-08-dcm-using-kcl/index.md +++ b/i18n/zh-CN/docusaurus-plugin-content-blog/2023-09-08-dcm-using-kcl/index.md @@ -108,8 +108,8 @@ spec: params: name: app containers: - ngnix: - image: ngnix + nginx: + image: nginx ports: - containerPort: 80 service: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/concepts/type-and-definition.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/concepts/type-and-definition.md index 085d1961..7331c007 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/concepts/type-and-definition.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.4.6/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.4.6/user_docs/guides/abstraction.md index c2f17db8..5c7b1241 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.4.6/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.4.6/user_docs/guides/abstraction.md @@ -54,15 +54,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -74,7 +74,7 @@ app.App { $ kcl main.k docker_compose_render.k services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -104,8 +104,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.0/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.0/user_docs/guides/abstraction.md index 23b1f3fc..5aa6369f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.0/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.0/user_docs/guides/abstraction.md @@ -54,15 +54,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -79,7 +79,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -114,8 +114,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.1/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.1/user_docs/guides/abstraction.md index 23b1f3fc..5aa6369f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.1/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.1/user_docs/guides/abstraction.md @@ -54,15 +54,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -79,7 +79,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -114,8 +114,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.2/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.2/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.2/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.2/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.3/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.3/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.3/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.3/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/concepts/type-and-definition.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/concepts/type-and-definition.md index 085d1961..7331c007 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/concepts/type-and-definition.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.4/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/concepts/type-and-definition.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/concepts/type-and-definition.md index 085d1961..7331c007 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/concepts/type-and-definition.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.5/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/concepts/type-and-definition.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/concepts/type-and-definition.md index 085d1961..7331c007 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/concepts/type-and-definition.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.5.6/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/concepts/type-and-definition.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/concepts/type-and-definition.md index 085d1961..7331c007 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/concepts/type-and-definition.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.6.0/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/concepts/type-and-definition.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/concepts/type-and-definition.md index 085d1961..7331c007 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/concepts/type-and-definition.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/guides/abstraction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/guides/abstraction.md index 5e61d174..46e448b5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/guides/abstraction.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/guides/abstraction.md @@ -58,15 +58,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `ngnix` 容器,并开启 `80` 端口配置。 +在上面的代码中,我们使用 `App` schema 定义了一个配置,其中我们配置了一个 `nginx` 容器,并开启 `80` 端口配置。 此外,KCL 允许开发人员以声明式的方式定义应用程序所需的资源,并允许生成特定于平台的配置文件,如 `docker_compose.yaml` 或 Kubernetes `manifests.yaml` 文件。接下来,让我们生成相应的配置。 @@ -83,7 +83,7 @@ kcl main.k docker_compose_render.k ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -118,8 +118,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.4.6/user_docs/guides/abstraction.md b/versioned_docs/version-0.4.6/user_docs/guides/abstraction.md index e134c679..203fe2fe 100644 --- a/versioned_docs/version-0.4.6/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.4.6/user_docs/guides/abstraction.md @@ -56,15 +56,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -76,7 +76,7 @@ If we want to transform the application config into the docker compose config, w $ kcl main.k docker_compose_render.k services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -106,8 +106,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.0/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.0/user_docs/guides/abstraction.md index a2053556..f3c8db98 100644 --- a/versioned_docs/version-0.5.0/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.0/user_docs/guides/abstraction.md @@ -56,15 +56,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -81,7 +81,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -116,8 +116,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.1/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.1/user_docs/guides/abstraction.md index a2053556..f3c8db98 100644 --- a/versioned_docs/version-0.5.1/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.1/user_docs/guides/abstraction.md @@ -56,15 +56,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -81,7 +81,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -116,8 +116,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.2/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.2/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.5.2/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.2/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.3/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.3/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.5.3/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.3/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.4/user_docs/concepts/type-and-definition.md b/versioned_docs/version-0.5.4/user_docs/concepts/type-and-definition.md index 0801b746..ed82315f 100644 --- a/versioned_docs/version-0.5.4/user_docs/concepts/type-and-definition.md +++ b/versioned_docs/version-0.5.4/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/versioned_docs/version-0.5.4/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.4/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.5.4/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.4/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.5/user_docs/concepts/type-and-definition.md b/versioned_docs/version-0.5.5/user_docs/concepts/type-and-definition.md index 0801b746..ed82315f 100644 --- a/versioned_docs/version-0.5.5/user_docs/concepts/type-and-definition.md +++ b/versioned_docs/version-0.5.5/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/versioned_docs/version-0.5.5/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.5/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.5.5/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.5/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.5.6/user_docs/concepts/type-and-definition.md b/versioned_docs/version-0.5.6/user_docs/concepts/type-and-definition.md index 0801b746..ed82315f 100644 --- a/versioned_docs/version-0.5.6/user_docs/concepts/type-and-definition.md +++ b/versioned_docs/version-0.5.6/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/versioned_docs/version-0.5.6/user_docs/guides/abstraction.md b/versioned_docs/version-0.5.6/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.5.6/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.5.6/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.6.0/user_docs/concepts/type-and-definition.md b/versioned_docs/version-0.6.0/user_docs/concepts/type-and-definition.md index 0801b746..ed82315f 100644 --- a/versioned_docs/version-0.6.0/user_docs/concepts/type-and-definition.md +++ b/versioned_docs/version-0.6.0/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/versioned_docs/version-0.6.0/user_docs/guides/abstraction.md b/versioned_docs/version-0.6.0/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.6.0/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.6.0/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80 diff --git a/versioned_docs/version-0.7.0/user_docs/concepts/type-and-definition.md b/versioned_docs/version-0.7.0/user_docs/concepts/type-and-definition.md index 0801b746..ed82315f 100644 --- a/versioned_docs/version-0.7.0/user_docs/concepts/type-and-definition.md +++ b/versioned_docs/version-0.7.0/user_docs/concepts/type-and-definition.md @@ -17,7 +17,7 @@ where $k$ is the attribute name, $v$ is the attributes value, and $T$ is the typ By default, KCL does not require type annotations and performs type checks at runtime. ```python -name = "ngnix" # The type of `name` is `str` +name = "nginx" # The type of `name` is `str` port = 80 # The type of `port` is `int` ``` diff --git a/versioned_docs/version-0.7.0/user_docs/guides/abstraction.md b/versioned_docs/version-0.7.0/user_docs/guides/abstraction.md index f6dc6de7..87e85631 100644 --- a/versioned_docs/version-0.7.0/user_docs/guides/abstraction.md +++ b/versioned_docs/version-0.7.0/user_docs/guides/abstraction.md @@ -60,15 +60,15 @@ import .app app.App { name = "app" - containers.ngnix = { - image = "ngnix" + containers.nginx = { + image = "nginx" ports = [{containerPort = 80}] } service.ports = [{ port = 80 }] } ``` -In the above code, we defined a configuration using the `App` schema, where we configured an `ngnix` container and configured it with an `80` service port. +In the above code, we defined a configuration using the `App` schema, where we configured an `nginx` container and configured it with an `80` service port. Besides, KCL allows developers to define the resources required for their applications in a declarative manner and is tied to a platform such as Docker Compose or Kubernetes manifests and allows to generate a platform-specific configuration file such as `docker-compose.yaml` or a Kubernetes `manifests.yaml` file. Next, let's generate the corresponding configuration. @@ -85,7 +85,7 @@ The output is ```yaml services: app: - image: ngnix + image: nginx ports: - published: 80 target: 80 @@ -120,8 +120,8 @@ spec: app: app spec: containers: - - name: ngnix - image: ngnix + - name: nginx + image: nginx ports: - protocol: TCP containerPort: 80