@@ -279,10 +279,18 @@ A module is a collection of packages that are released, versioned, and
279
279
distributed together. Modules are downloaded from OCI-compliant
280
280
artifact registries.
281
281
282
+ The Central Registry for CUE modules (` + modconfig .DefaultRegistry + `) is
283
+ used as the source for external modules by default.
284
+
282
285
For a detailed reference on modules:
283
286
284
287
https://cuelang.org/docs/reference/modules/
285
288
289
+ For tutorials on how to use the Central Registry, see:
290
+
291
+ https://cuelang.org/docs/tutorial/working-with-the-central-registry/
292
+ https://cuelang.org/docs/tutorial/publishing-modules-to-the-central-registry/
293
+
286
294
For a tutorial on how to work with a custom OCI registry for CUE modules:
287
295
288
296
https://cuelang.org/docs/tutorial/working-with-a-custom-module-registry/
@@ -303,8 +311,8 @@ Given a particular registry configuration, it's possible to work what registry a
303
311
given module is stored in, and what repository within that registry, without
304
312
making any network calls.
305
313
306
- If no explicit registry configuration is present, a default central registry
307
- (` + modconfig .DefaultRegistry + `) will be used for all modules.
314
+ If no explicit registry configuration is present, a default Central Registry
315
+ (` + modconfig .DefaultRegistry + `) is used for all modules.
308
316
309
317
The simplest way of specifying a registry configuration is to set $CUE_REGISTRY
310
318
to the hostname of that registry.
0 commit comments