Platform Team/Server Kit/sugar-server

Summary

The core Sugar Server Kit component.

The singular program requires only Python, and obvious dependencies like coreutils, to allow all its services to function properly. It provides basic sugar related services, and uses one CLI tool to manage all its functionality.

Services

The list of services that sugar-server provides.

id

Provide Sugar users registration on a school server. After being registered, Sugar on users side will setup interaction with a school server, such as:

• jabber sever in /desktop/sugar/collaboration/jabber_server GConf setting,
• backup url in /desktop/sugar/backup_url GConf setting,
• Package Management System configuration file in ~/.sugar/profile/pms.conf to upgrade packages on client side.

Later, these settings will be used by sugar-client to process its regular routines.

collector

Collect usage statistics gathered by sugar-client in monitor mode for later analyzing.

Requires

• bios-crypto
  bios-crypto client utilities are being used in anti-thief support and should be installed only if sign service is being used.
• python-mysql
  If the rest of school server applications use MySql, it might be useful to keep sugar-server data in MySql as well. Otherwise plain text file will be used.

Configuration

By default, configuration occurs based on several sources (sorted by applied order):

• /etc/sugar-server.conf system-wide configuration file,
• ~/.local/sugar-server/config user-wide configuration file,
• sugar-server's command-line arguments.

Configuration files contain option names equal to command-line arguments. To get the current configuration, call:

sugar-server config

See sugar-server-templates sources for an example.

Getting involved

• Report on bugs.
• Read the HACKING file to know how to contribute with code.

Resources

• Sources.