From d8a30203ce6fa0bfb2ff9d90395ff0a25240ceec Mon Sep 17 00:00:00 2001 From: Joshua Holbrook Date: Thu, 20 Oct 2011 13:54:47 -0700 Subject: [PATCH] [fix] filename --> file in a few file transport examples --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 8390468..1a9a946 100644 --- a/README.md +++ b/README.md @@ -59,8 +59,8 @@ The top-level of `nconf` is an instance of the `nconf.Provider` abstracts this a Adds a new store with the specified `name` and `options`. If `options.type` is not set, then `name` will be used instead: ``` js - nconf.add('global', { type: 'file', filename: '/path/to/globalconf.json' }); - nconf.add('userconf', { type: 'file', filename: '/path/to/userconf.json' }); + nconf.add('global', { type: 'file', file: '/path/to/globalconf.json' }); + nconf.add('userconf', { type: 'file', file: '/path/to/userconf.json' }); ``` ### nconf.use(name, options) @@ -70,12 +70,12 @@ Similar to `nconf.add`, except that it can replace an existing store if new opti // // Load a file store onto nconf with the specified settings // - nconf.use('file', { filename: '/path/to/some/config-file.json' }); + nconf.use('file', { file: '/path/to/some/config-file.json' }); // // Replace the file store with new settings // - nconf.use('file', { filename: 'path/to/a-new/config-file.json' }); + nconf.use('file', { file: 'path/to/a-new/config-file.json' }); ``` ### nconf.remove(name) @@ -186,4 +186,4 @@ Tests are written in vows and give complete coverage of all APIs and storage eng #### Author: [Charlie Robbins](http://nodejitsu.com) -[0]: http://github.com/indexzero/nconf \ No newline at end of file +[0]: http://github.com/indexzero/nconf