#holochain #conductor #admin #info #dump #response #cell

holochain_conductor_api

Message types for Holochain admin and app interface protocols

167 releases

new 0.3.0-beta-dev.46 Apr 24, 2024
0.3.0-beta-dev.42 Mar 27, 2024
0.3.0-beta-dev.29 Dec 22, 2023
0.3.0-beta-dev.26 Nov 29, 2023
0.0.2 Jul 29, 2021

#1906 in Magic Beans

Download history 9/week @ 2024-01-01 189/week @ 2024-01-08 122/week @ 2024-01-15 167/week @ 2024-01-22 160/week @ 2024-01-29 380/week @ 2024-02-05 81/week @ 2024-02-12 225/week @ 2024-02-19 451/week @ 2024-02-26 635/week @ 2024-03-04 410/week @ 2024-03-11 799/week @ 2024-03-18 164/week @ 2024-03-25 556/week @ 2024-04-01 672/week @ 2024-04-08 569/week @ 2024-04-15

1,985 downloads per month
Used in 15 crates (8 directly)

Apache-2.0 and AGPL-3.0 WITH mif-exception

1MB
25K SLoC

holochain_conductor_api

License: Apache-2.0


lib.rs:

Interfaces to manage Holochain applications (hApps) and call their functions.

The Conductor is the central component of Holochain. It exposes WebSockets for clients to connect to, processes incoming requests and orchestrates data flow and persistence.

Refer to Holochain's architecture for more info. Read about hApp development in the Happ Development Kit (HDK) documentation.

There is a Holochain client for JavaScript and a Rust client to connect to the Conductor.

The Conductor API is split into Admin and App requests and responses. Each has an associated enum AdminRequest and AppRequest that define and document available calls.

The admin interface generally manages the conductor itself, such as installing apps, listing dnas, cells and apps, accessing state and metric information dumps and managing agents.

The app interface is smaller and focussed on interfacing with an app directly. Notably the app interface allows calling functions exposed by the hApps' modules, called DNAs. To discover a particular hApp's structure, its app info can be requested.

Dependencies

~64–100MB
~2M SLoC