diff options
author | Michael Klein <mischkl@users.noreply.github.com> | 2015-05-08 16:31:08 +0300 |
---|---|---|
committer | Forrest L Norvell <forrest@npmjs.com> | 2015-05-15 04:11:46 +0300 |
commit | f70dea9b4766f6eaa55012c3e8087e9cb04fd4ce (patch) | |
tree | 91b8146c98852e0988fab9cf9552467150b30ef7 /doc | |
parent | 79f8a9664199c638d7fd576a4830a15ee9813af2 (diff) |
doc: clarify the use of --registry
The ability to use the --registry option for individual publish commands
somehow seemed buried. I've put it in its own paragraph and added "for
that publish command" in order to make things clearer.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/misc/npm-registry.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/misc/npm-registry.md b/doc/misc/npm-registry.md index b0487f6df..0875a5d4e 100644 --- a/doc/misc/npm-registry.md +++ b/doc/misc/npm-registry.md @@ -31,9 +31,10 @@ similar) design doc to implement the APIs. If you set up continuous replication from the official CouchDB, and then set your internal CouchDB as the registry config, then you'll be able to read any published packages, in addition to your private ones, and by -default will only publish internally. If you then want to publish a -package for the whole world to see, you can simply override the -`--registry` config for that command. +default will only publish internally. + +If you then want to publish a package for the whole world to see, you can +simply override the `--registry` option for that `publish` command. ## I don't want my package published in the official registry. It's private. |