You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/understanding-configuration-file.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
[id="understanding-configuration-file"]
9
9
= Understanding the {productname} configuration file
10
10
11
-
Whether deployed on premise of by the {productname-ocp} Operator, the registry's behavior is defined by the `config.yaml` file. The `config.yaml` file must include all required configuration fields for the registry to start. {productname} administrators can also define optional parameters that customize their registry, such as authentication parameters, storage parameters, proxy cache parameters, and so on.
11
+
Whether deployed on premise or by the {productname-ocp} Operator, the registry's behavior is defined by the `config.yaml` file. The `config.yaml` file must include all required configuration fields for the registry to start. {productname} administrators can also define optional parameters that customize their registry, such as authentication parameters, storage parameters, proxy cache parameters, and so on.
12
12
13
13
The `config.yaml` file must be written using valid YAML ("YAML Ain't Markup Language") syntax, and {productname} cannot start if the file itself contains any formatting errors or missing required fields. Regardless of deployment type, whether that is on premise or {productname-ocp} that is configured by the Operator, the YAML principles stay the same, even if the required configuration fields are slightly different.
0 commit comments