Hive: Difference between revisions
Jump to navigation
Jump to search
Adamcolton (talk | contribs) Created page with "This is responsible for managing local resources. Hive boots up waxnet and manages which waxnet apps are running. It configures storage. New apps are installed through Hive. ..." |
Adamcolton (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
One of the keys is that Hive uses the [[TrustGraph]]. Only apps that have been vetted by your trust network (or that you trust directly) will even be displayed for installation. | One of the keys is that Hive uses the [[TrustGraph]]. Only apps that have been vetted by your trust network (or that you trust directly) will even be displayed for installation. | ||
== Git+Bugs == | |||
We're going to need git integration for source control as well as a bug tracking system. It's a little down the road but worth thinking about. | |||
== Routing == | |||
Hive acts as a message router between services. Hive starts up all services and applications. So they can all communicate with Hive over std in/out. This prevents exposing calls via RPC. | |||
[[Category:Waxnet]] | [[Category:Waxnet]] | ||
Latest revision as of 16:45, 2 March 2016
This is responsible for managing local resources. Hive boots up waxnet and manages which waxnet apps are running. It configures storage. New apps are installed through Hive.
One of the keys is that Hive uses the TrustGraph. Only apps that have been vetted by your trust network (or that you trust directly) will even be displayed for installation.
Git+Bugs
We're going to need git integration for source control as well as a bug tracking system. It's a little down the road but worth thinking about.
Routing
Hive acts as a message router between services. Hive starts up all services and applications. So they can all communicate with Hive over std in/out. This prevents exposing calls via RPC.