Platform Team/Server Kit/Mace: Difference between revisions

Line 37:

In addition to configuration files, Mace can process files with a {{Code|.env}} suffix. These files contain variable declarations in Bash syntax. The values of these variables might be entered in configuration files in the form of {{Code|@VARIABLE@}}, in which case they will be expanded to real values while applying the configuration.

~~=== Providers ===~~

~~Mace supports only a limited number of services that might be configured. That's because Mace is supposed to be used mostly as a school server configuration tool.~~

~~See this auto generated from sources [http://api.sugarlabs.org/mace/pages/providers.html documentation] for the current list of supported providers.~~

== Configuration application ==

Line 60:

Line 54:

If the sources path is not the default, {{Code|/etc/sugar-server}}, use the {{Code|--input}} argument to specify the right one.

== Providers ==

Providers is the way how Mace can configure particular services. Providers don't contain high-level configuration logic, configuration will happen only basing on configuration sources passed to the Mace to process by these providers. At the same time, providers might do some extra work, e.g.,

to make sure that service's directory are created.

Mace supports only a limited number of [http://api.sugarlabs.org/mace/pages/providers.html#supported-systems GNU/Linux distributions] and [http://api.sugarlabs.org/mace/pages/providers.html#list-of-providers services]. That's because Mace is supposed to be used mostly as a school server configuration tool.

== Templates ==

Line 107:

Line 108:

== Getting involved ==

* Read [http://api.sugarlabs.org/mace/pages/HACKING.html HACKING] file,

Please read [http://api.sugarlabs.org/mace/pages/HACKING.html HACKING] file.

* ~~Read~~ [http://api.sugarlabs.org/mace ~~documentation~~] auto generated from sources.

== Resources ==

* [http://git.sugarlabs.org/server/mace Sources].

* [http://api.sugarlabs.org/mace Documentation] auto generated from sources.

@@ Line 37: / Line 37: @@
 In addition to configuration files, Mace can process files with a {{Code|.env}} suffix. These files contain variable declarations in Bash syntax. The values of these variables might be entered in configuration files in the form of {{Code|@VARIABLE@}}, in which case they will be expanded to real values while applying the configuration.
-=== Providers ===
-Mace supports only a limited number of services that might be configured. That's because Mace is supposed to be used mostly as a school server configuration tool.
-See this auto generated from sources [http://api.sugarlabs.org/mace/pages/providers.html documentation] for the current list of supported providers.
 == Configuration application ==
@@ Line 60: / Line 54: @@
 If the sources path is not the default, {{Code|/etc/sugar-server}}, use the {{Code|--input}} argument to specify the right one.
+== Providers ==
+Providers is the way how Mace can configure particular services. Providers don't contain high-level configuration logic, configuration will happen only basing on configuration sources passed to the Mace to process by these providers. At the same time, providers might do some extra work, e.g.,
+to make sure that service's directory are created.
+Mace supports only a limited number of [http://api.sugarlabs.org/mace/pages/providers.html#supported-systems GNU/Linux distributions] and [http://api.sugarlabs.org/mace/pages/providers.html#list-of-providers services]. That's because Mace is supposed to be used mostly as a school server configuration tool.
 == Templates ==
@@ Line 107: / Line 108: @@
 == Getting involved ==
-* Read [http://api.sugarlabs.org/mace/pages/HACKING.html HACKING] file,
+Please read [http://api.sugarlabs.org/mace/pages/HACKING.html HACKING] file.
-* Read [http://api.sugarlabs.org/mace documentation] auto generated from sources.
+== Resources ==
+* [http://git.sugarlabs.org/server/mace Sources].
+* [http://api.sugarlabs.org/mace Documentation] auto generated from sources.