Platform Team/Sugar Network/Implementation

Sugar Network version cycle: | 1.0 |

Summary

The design and implementation are tailored by the following intentions:

• Implementation should be as lightweight as possible to run all components on restricted hardware like XO laptops;
• Minimize any maintaining costs as much as possible to use Sugar Network in environments like offline schools where the only maintainers are not IT skilled people;
• Assume decentralization scheme when Sugar Network nodes might be started on different servers with further online or offline synchronization with the master.

To accomplish above tasks, Sugar Network content is handled by the active-document library which uses Xapian to index content and simple filesystem storage (might be changed in the future).

Sugar Network is represented by two major applications to run on Sugar Network node or users side:

• sugar-network-node, and,
• sugar-network-client.

In both cases, applications provide RESTful API as the only access point for outer usage. Any end users related functionality implemented in Sugar Network clients on top of API providers.

Usage

Install sugar-network package from the Factory repository from Sweets Distribution or checkout sources from Gitorious:

git clone git://git.sugarlabs.org/network/network.git --recurse-submodules

See Also

• Sugar Network API.
• Distribution options.
• Sugar Network clients.

Getting involved

• Submit your bug report or feature request.
• Browse our implementation discussions, and post your feedback. (You should join this discussion list in order to avoid having your messages postponed for moderation.)