There are many reasons to use an ephemeral graph system, here's some highlights
...
...
@@ -58,7 +58,7 @@ For https://bip.io hosted users, bipio has 2 endpoints that you'll likely be usi
### Authentication
The API uses [HTTP Basic Authentication](http://en.wikipedia.org/wiki/Basic_access_authentication). Username will be your account username, and password is a generated API token.
The API uses [HTTP Basic Authentication](http://en.wikipedia.org/wiki/Basic_access_authentication). Username will be your account username, and password is a generated API token.
@@ -85,7 +85,7 @@ You can expose an account UUID by shelling into mongodb and running the appropri
Most REST resources also have additional response decorators attached to each model which provides a little extra info. Decorators are prefixed with an underscore and are read-only. eg: `_href : "https://docs.bip.io/rest/bip/bc928113-0a98-4975-a821-98373aa72552"`
The two most common are
The two most common are
***_href** (URI) Fully Qualified Resource URI
***_repr** (String) Derived representation.
...
...
@@ -120,7 +120,7 @@ GET /rest/domain?page=1&page_size=10&order_by=recent
}
```
### RPC
### RPC
[RPC's](http://en.wikipedia.org/wiki/Remote_procedure_call) provide certain behaviors and helpers for performing work, negotiating authentication or generating content.
...
...
@@ -163,7 +163,7 @@ The first time you setup bipio via `make install`, it will ask you some question
***public_interfaces** (array, optional) list of resolvable IP's (V4|V6) for internal domain resolution. omit to autodiscover.
***ssl** (object, optional) key and certificate paths for SSL