dweb-registry
API Registry Client for publishing dwebs. By default, the client is capable of registering, login, and publishing to registry.dwebx.net.
dweb-registry
allows users to interact with and publish dwebs to your registry via the dweb
command line. Supporting this module on your registry will allow a user to login and publish:
dweb login custom-dweb-registry.com
dweb publish
Installation
npm install dweb-registry
Quick Example
var Registry = var registry = registry
API
var registry = Registry([opts])
opts.server
: the registry server. Default ishttps://registry.dwebx.net
opts.apiPath
: registery server API path, e.g. we use/api/v1
for registry.dwebx.net. This will overwrite default township routes to use server + apiPath.opts.config.filename
: defaults to~.datrc
instead of township defaults.
Other options are passed to township-client, these include:
opts = config: filepath: '~/.townshiprc' // specify a full config file path routes: // routes for ALL township servers used by client register: '/register' login: '/login' updatePassword: '/updatepassword'
registry.login(data, cb)
Requires data.email
and data.password
.
registry.register(data, cb)
Requires data.username
, data.email
, and data.password
.
registry.logout(cb)
Will callback with logout success or failure.
var user = registry.whoami([opts])
Returns user object with currently logged in user. See township-client
for options.
CRUD API
registry.dwebs.create(data, cb)
Must be logged in. Requires a unique data.name
and unique data.url
. DWeb will be immediately available on the /:username/:name
.
Accepts also any fields in a dweb.json
file.
registry.dwebs.get([data], cb)
Returns all dwebs that match the given (optional) querystrings.