About

Portfolio is a system for managing, synchronizing personal documents, including multiple deployed storage nodes and clients.

If you think keeping, saving and managing and sorting your documents on your own computer is essential, then Portfolio is the solution for you!

Portfolio is currently a demo version. Users must take care of their files uploaded to the server, usually a personal computer.

The Topology

The v0.8.# Demo version automatically sychronize files that users uploaded to any of the server, in the user’s synchronization domain. Here after the file strage node is named as a Synode.

-------------------
|    domain-hub    |
|    ^       ^     |
|    |       |     |
| node-1    node-1 |
-------------------
    ^         ^
    |         |
mobile-1   device-2 ...

domain-hub: The server can be accessed via public IP

node 1 & 2: The private file storage, typically a personal computer.

This structure is based on an Edge Computing backbone, and the developer(s) is planning to extend this to peer-peer nodes without any network topology restriction.

About Volume

A volume is a folder within the server’s file system, which is specified by the user while setting up the service node. uploaded files and data are saved there.

Warning

Don’t change data in the volume folder. Moving, modification of files will cause unspecified results.

Also, do not switch volume to another location although in v 0.7.0 the service can still run.

Limitation of Portfolio 0.8

Needing a hub syndoe deployed on a public IP host, which can be accessed by other synnodes.
Only fixed number of Synodes and cannot be changed.
File storage limitation is low - price for hub storage can be high.

What you can expect in the near future

A cloud service that users can plan their domains.
The hub node can schedule storage, by keeping only public accessable files.
Synodes can join and leave the domain.

FYI, the Edge Computing backbone of Portfolio can do a lot more. Here is the the detailed techquenical discussion.