Platform Team/Server Kit/Architecture: Difference between revisions
No edit summary |
No edit summary |
||
| Line 75: | Line 75: | ||
* [[The_Server/sugar-server|sugar-server]] provides basic sugar specific services, | * [[The_Server/sugar-server|sugar-server]] provides basic sugar specific services, | ||
* [[The_Server/sugar-server-base|sugar-server-base]] | * [[The_Server/sugar-server-base|sugar-server-base]] provides configuration only for basic external services that need to be installed and configured on bare servers at school, | ||
* [[The_Server/Mace|mace]] process configuration sources, e.g., from sugar-server-base. | * [[The_Server/Mace|mace]] process configuration sources, e.g., from sugar-server-base. | ||
The only | The only relationship between them are: | ||
* sugar-server might be configured from sugar-server-base | * sugar-server might be configured from sugar-server-base | ||
* sugar-server-base makes sense only after processing its content by mace | * sugar-server-base makes sense only after processing its content by mace | ||
These are building | These are building blocks for the final solutions in downstream deployments. Components are optional, meaning that | ||
* sugar-server might be used in the singular manner | * sugar-server might be used in the singular manner; it doesn't need any special (outside of sugar-server) configuration, and can be started even from its sources directory; | ||
* sugar-server-base might be used in the singular manner | * sugar-server-base might be used in the singular manner (but obviously with the mace) to configure only non Sugar services; | ||
* mace might be used in the singular manner to configure any services. | * mace might be used in the singular manner to configure any services. | ||