Deployment Platform/Client Configuration

< Deployment Platform
Revision as of 10:37, 4 June 2013 by Alsroot (talk | contribs) (Created page with "== Summary == This page describes the {{Code|sweets.conf}} configuration file, the common way to configure Sugar clients within the Sweets Distribution, thus, [[Deploymen...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Summary

This page describes the sweets.conf configuration file, the common way to configure Sugar clients within the Sweets Distribution, thus, Deployment Platform. Configuration does not intersect with Sugar Shell settings, stored in GConf, and contains parameters related only to new functionality introduced by Sweets Distribution.

Configuration files

The configuration occurs based on several sources (sorted by applied order):

  • /etc/sweets.conf
    system-wide configuration file,
  • ~/.config/sweets/config
    user-wide configuration file,
  • ~/.sugar/PROFILE/sweets.conf
    configuration related to particular Sugar profile.

Configuration files should be formatted as regular INI files.

Configuration sections

This is a list of configuration sections in sweets.conf files. Each section belongs to particular application and might be optional in the final system.

[client]

Configure sugar-network-client, a Sugar Network client application from sugar-network package. To get the full list of available configure options, call the sugar-network-client config command.

[shell]

Configure Sugar Shell extra functionality implemented by version packaged in Sweets Distribution. There are the following settings:

[blacklist]

Blacklist Sugar Shell components.

[sugar-plugin-*]

Configure particular Shell plugin.