cascade/ipfs-cluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update code layout desc in architecture.md

Browse Source 
License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>
This commit is contained in:
Hector Sanjuan 2017-03-14 16:47:48 +01:00
parent e2efef8469
commit b4dd8dd9c6
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
architecture.md
View File

@ -55,7 +55,7 @@ On the down-side, the RPC API involves "reflect" magic and it is not easy to ver
### Code layout
Eventually, as the project grow, components will be organized in different submodules. The groundwork for this is already there (i.e. a there is a submodule providing API related types), but most components still live in the base project.
Components are organized in different submodules (i.e. `pintracker/maptracker` represents component `PinTracker` and implementation `MapPinTracker`). Interfaces for all components are on the base module. Executables (`ipfs-cluster-service` and `ipfs-cluster-ctl` are also submodules to the base module).
## Applications