Difference between revisions of "Platform Team/Server Kit/sugar-server"
< Platform Team | Server Kit
Jump to navigation
Jump to search
m (→Configuration) |
|||
| Line 20: | Line 20: | ||
== Configuration == | == Configuration == | ||
| − | By default, configuration | + | By default, configuration occurs based on several sources (sorted by applied order): |
* {{Code|/etc/sugar-server.conf}} system-wide configuration file, | * {{Code|/etc/sugar-server.conf}} system-wide configuration file, | ||
| Line 26: | Line 26: | ||
* {{Code|sugar-server}}'s command-line arguments. | * {{Code|sugar-server}}'s command-line arguments. | ||
| − | Configuration files contain | + | Configuration files contain option names equal to command-line arguments. To get the current configuration, call: |
sugar-server config | sugar-server config | ||
Revision as of 12:51, 26 August 2011
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
- Required services:
- Student identification
- Optional services:
- XO anti-thief support
- Entire Journal backup/restore
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.confsystem-wide configuration file,~/.local/sugar-server/configuser-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.