Deployment Platform/Client Configuration
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.
The configuration occurs based on several sources (sorted by applied order):
directory with system-wide configuration files,
system-wide configuration file,
user-wide configuration file,
configuration related to particular Sugar profile.
Configuration files should be formatted as regular INI files.
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.
General purpose section.
Logging verbosity level:
0, log only errors and warning,
1, additionally log info messages,
2, additionally log debug messages,
3, additionally log trace messages.
One more Sugar Network related section. By default, only stable Sugar Activity implementations will be fetched from the Sugar Network. To customize stability selection, add exceptions to the this section. Each option should conform the format
CONTEXT = STABILITIES.
[stabilities] org.somosazucar.ServidorVNC = stable,testing
Configure Sugar Shell extra functionality implemented by version packaged in Sweets Distribution. There are the following settings:
Space separated list of Shell plugins to enable.
Blacklist Sugar Shell components.
Configure particular Shell plugin.
Configure PackageKit presolve backend.