|
Size: 1575
Comment: Remove "future developments" notice. The future is upon us!
|
Size: 1698
Comment: Remove off-topic portal link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma section-numbers off |
|
| Line 3: | Line 5: |
| = For everyone... = | [[TableOfContents]] |
| Line 5: | Line 7: |
| * DomTool/UserGuide: An introduction to configuring shared daemons at HCoop * ["DomTool/Examples"]: A smorgasbord of example configuration snippets * DomTool/LanguageReference: A complete description of the programming language used for configuration files * [http://deleuze.hcoop.net/domtool/ Standard library reference], including all of the primitive actions for configuring shared daemons |
= For everyone = |
| Line 10: | Line 9: |
| = For admins (and the curious)... = | * '''[:DomTool/UserGuide:User Guide]''': An introduction to configuring shared daemons at HCoop. * '''[:DomTool/Examples: Working Examples]''': A smorgasbord of example configuration snippets. * [:DomTool/LanguageReference:Language Reference]: A complete description of the programming language used for configuration files. * [http://deleuze.hcoop.net/domtool/ Standard Library Reference], including all of the primitive actions for configuring shared daemons. |
| Line 12: | Line 14: |
| * DomTool/AdminProcedures: The daily care and feeding of DomTool | = For admins (and the curious) = * DomTool/AdminProcedures: The daily care and feeding of DomTool. |
| Line 14: | Line 18: |
| * ["DomTool/Plugins"]: Descriptions of the different plugins responsible for configuring various daemons, including how they publish their configuration for those daemons to use | * ["DomTool/Plugins"]: Descriptions of the different plugins responsible for configuring various daemons, including how they publish their configuration for those daemons to use. |
| Line 16: | Line 20: |
| * DomTool/SslProcedures: How to set up the various certificates used by the domtool clients and servers * ["DomTool/Building"]: Obtaining and building the DomTool source * ["DomTool/Implementation"]: Details on the implementation of the DomTool tools * ["DomTool/Debugging"]: Some tricks to do manually what DomTool usually does automatically |
* DomTool/SslProcedures: How to set up the various certificates used by the domtool clients and servers. * ["DomTool/Building"]: Obtaining and building the DomTool source. * ["DomTool/Implementation"]: Details on the implementation of the DomTool tools. * ["DomTool/Debugging"]: Some tricks to do manually what DomTool usually does automatically. |
This is the master page for information on HCoop's distributed system configuration tool.
For everyone
[:DomTool/UserGuide:User Guide]: An introduction to configuring shared daemons at HCoop.
[:DomTool/Examples: Working Examples]: A smorgasbord of example configuration snippets.
[:DomTool/LanguageReference:Language Reference]: A complete description of the programming language used for configuration files.
[http://deleuze.hcoop.net/domtool/ Standard Library Reference], including all of the primitive actions for configuring shared daemons.
For admins (and the curious)
DomTool/AdminProcedures: The daily care and feeding of DomTool.
DomTool/ArchitectureOverview: How does this beast work, anyway?
- ["DomTool/Plugins"]: Descriptions of the different plugins responsible for configuring various daemons, including how they publish their configuration for those daemons to use.
DomTool/AdditionalClients: Several other command-line tools mentioned elsewhere on this wiki are really DomTool clients. This page collects notes on their implementations.
DomTool/SslProcedures: How to set up the various certificates used by the domtool clients and servers.
["DomTool/Building"]: Obtaining and building the DomTool source.
["DomTool/Implementation"]: Details on the implementation of the DomTool tools.
["DomTool/Debugging"]: Some tricks to do manually what DomTool usually does automatically.
Old pages
DomainTool describes the previous version of domtool.
DomtoolTwo is the preview added by AdamChlipala before we began migrating to our new servers.