Difference between revisions of "Platform Team/Server Kit/sugar-server-templates"

From Sugar Labs
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This component contains only configuration of basic external services that need to be installed and configured on bare servers at school.
+
== Summary ==
 +
 
 +
This component contains configuration templates of basic services that need to be installed and configured on bare servers at school. It is possible to peek at some of these services in a downstream solution to apply using the [[Sugar_Server_Kit/Mace|mace]] utility. See the [[Sugar_Server_Kit/sugar-server-demoxo|demoxo]] demonstration project for example.
 +
 
 +
== Services ==
 +
 
 +
The set of services need not be limited to a single-solution per feature, i.e., it might contain configurations for several implementations of the same feature.
  
 
These services are:
 
These services are:
Line 12: Line 18:
 
* DHCP
 
* DHCP
  
== Sources ==
+
== Getting involved ==
 +
 
 +
* [http://bugs.sugarlabs.org/newticket?component=sugar-server-kit Report] on bugs.
 +
* Read the [http://git.sugarlabs.org/server/templates/blobs/master/HACKING HACKING] file to know how to contribute with code.
 +
 
 +
== Resources ==
  
* http://git.sugarlabs.org/server/base
+
* [http://git.sugarlabs.org/server/templates Sources].

Latest revision as of 04:48, 21 March 2012

Summary

This component contains configuration templates of basic services that need to be installed and configured on bare servers at school. It is possible to peek at some of these services in a downstream solution to apply using the mace utility. See the demoxo demonstration project for example.

Services

The set of services need not be limited to a single-solution per feature, i.e., it might contain configurations for several implementations of the same feature.

These services are:

  • System configuration like iptables and sudo
  • Jabber
  • Web cache
  • Content filter
  • SSH
  • NTP
  • DNS
  • DHCP

Getting involved

  • Report on bugs.
  • Read the HACKING file to know how to contribute with code.

Resources