@@ -30,7 +30,7 @@ ksonnet's package management schema can be summed up as follows:
### Application
A ksonnet application represents a well-structured directory of Kubernetes [manifests](#manifest). This directory is autogenerated by [`ksonnet init`](/docs/cli-reference/ksonnet_init.md). These manifests typically tie together in some way—for example, they might collectively define a web service like the following:
A ksonnet application represents a well-structured directory of Kubernetes [manifests](#manifest). This directory is autogenerated by [`ks init`](/docs/cli-reference/ks_init.md). These manifests typically tie together in some way—for example, they might collectively define a web service like the following:
@@ -216,7 +216,12 @@ You can use *default* or *custom* registries:
* By **default**, ksonnet allows you do download *packages* from the [`ksonnet/parts/incubator`](https://github.com/ksonnet/parts/tree/master/incubator) registry.
* You can set up your own **custom** registry with `ks registry add`, which accepts **any valid Github path**. *Note that this path needs to point a directory with the following structure:*
* You can set up a registry with three different protocols:
***Github** - a Github URI
***Filesystem** - a valid path to a local registry
***Helm** - a URI to a Helm repository
A registry contains a `registry.yaml` file with directories containing packages similar to the following structure: