Permalink
Browse files

update readme

  • Loading branch information...
1 parent ca6bafb commit 3c1b25d7c16ece0ef57fc9cfb6ea99b4a7b4750e @js-n committed Dec 29, 2012
Showing with 9 additions and 2 deletions.
  1. +2 −1 README.md
  2. +7 −1 package.json
View
@@ -15,6 +15,7 @@ say you want to set up a local, private npm registry for certain modules, but yo
| | |x | ------> | private |
| | |y | <------ | registry |
| | | | 404 +------------+
+ | | | |
| | | | 'foo'? +---------------+
| | | | -----------------> | |
| | | | <----------------- | public |
@@ -38,7 +39,7 @@ setup your npm client:
List as many registries as you want in fall-back order as command line arguments when startingnpm-registry.
-## note: proxy is read-onlys
+## note: proxy is read-only
Only GET requests are allowed. Strange things happens when you send state-changing requests around willy-nilly, and that's probably not what you want. For example, to publish a module, you probably want to specify which registry you're publishing it to, eg
View
@@ -1,8 +1,14 @@
{
"name": "npm-delegate",
"version": "0.1.0",
- "description": "a hierarchical npm-registry proxy",
+ "description": "a hierarchical npm-registry proxy to make private registries easier",
"main": "npm-delegate.js",
+ "keywords": [
+ "npm",
+ "registry",
+ "private",
+ "proxy"
+ ],
"repository": "git@github.com:jden/npm-delegate.git",
"author": "jden <jason@denizac.org>",
"license": "MIT",

0 comments on commit 3c1b25d

Please sign in to comment.