Platform Team/Server Kit/Architecture: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
** Provide useful API for any new components; | ** Provide useful API for any new components; | ||
* Be a GNU/Linux distribution agnostic. It doesn't make much sense in case of having only Server on a school server and, e.g., installing Server from the ISO but it makes sense if downstream organizations ship their products based on the Server and having particular GNU/Linux distribution is important; | * Be a GNU/Linux distribution agnostic. It doesn't make much sense in case of having only Server on a school server and, e.g., installing Server from the ISO but it makes sense if downstream organizations ship their products based on the Server and having particular GNU/Linux distribution is important; | ||
* It is not only about supporting XO laptops but about any Sugar based | * It is not only about supporting XO laptops but about any Sugar based environments; | ||
* Up to 1000 students per server. | |||
== Components == | == Components == | ||
| Line 23: | Line 24: | ||
* Journal backup/restore | * Journal backup/restore | ||
* [[Features/Smart_Objects|Shared objects]] | * [[Features/Smart_Objects|Shared objects]] | ||
| The core component. | | The core component. The singular package with only python, and obvious ones like coreutils, dependency required to let its services function properly. | ||
|- | |- | ||
| [[#sugar-server-base|sugar-server-base]] | | [[#sugar-server-base|sugar-server-base]] | ||