Skip to content

Commit ae0ae08

Browse files
authored
Merge pull request #55 from datapartyjs/i2p-support
i2p support
2 parents 7a3c1ae + a5c6a7d commit ae0ae08

107 files changed

Lines changed: 927 additions & 433 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,2 @@
11
/dist
2+
/docs

README.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
# @dataparty/api
22
[![experimental](http://badges.github.io/stability-badges/dist/experimental.svg)](http://github.com/badges/stability-badges)[![license](https://img.shields.io/github/license/datapartyjs/api)](https://github.com/datapartyjs/dataparty-api/blob/master/LICENSE)
33

4-
ad-hoc cloud for the Web3.0 generation
4+
decentralized cloud framework for the Web3.0 generation.
5+
6+
Dataparty allows the app maker to decide how centralized or distributed they app should be and implement that vision rapidly.
57

68
* Documentation - [datapartyjs.github.io/dataparty-api](https://datapartyjs.github.io/dataparty-api)
79
* NPM - [npmjs.com/package/@dataparty/api](https://www.npmjs.com/package/@dataparty/api)
@@ -10,8 +12,18 @@ ad-hoc cloud for the Web3.0 generation
1012

1113
## Goals
1214

13-
The primary goal of `@dataparty/api` is to enable secure microservices development across all architectual domains with a single code base. This covers traditional clouds, peer-to-peer apps(with or without cloud backing), and hybrid clouds.
15+
The primary goal of `@dataparty/api` is to enable secure microservices development across all architectual domains with a single code base. This covers traditional clouds, peer-to-peer apps(with or without cloud backing), and hybrid clouds. Dataparty services are able to be run on servers, edge devices, or even directly in the browser or app. This means users of dataparty based apps can frequently run their own backend from with an app.
16+
17+
18+
## Features
19+
20+
A dataparty app/service typically consists of these parts:
1421

22+
* [Comms](https://datapartyjs.github.io/dataparty-api/module-Comms.html)
23+
* [Config](https://datapartyjs.github.io/dataparty-api/module-Config.html)
24+
* [Db](https://datapartyjs.github.io/dataparty-api/module-Db.html)
25+
* [Party](https://datapartyjs.github.io/dataparty-api/module-Party.html)
26+
* [Service](https://datapartyjs.github.io/dataparty-api/module-Service.html)
1527

1628

1729
## Roadmap

docs/CloudParty.html

Lines changed: 0 additions & 3 deletions
This file was deleted.

docs/DocumentFactory.html

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)