202013-01-14 07:07:24ClintonEbadi192013-01-14 07:07:12ClintonEbadicat / remove seemingly superfluous info about ip addresses182011-01-28 19:59:41laurenmcnees172008-07-07 04:28:15localhostconverted to 1.6 markup162008-04-30 15:13:24AdamChlipaladeleuze ~~> mail152008-04-20 15:44:11AdamChlipalans2 -> ns5142008-04-05 06:09:55MichaelOlsonRecommend mire_ip and deleuze_ip132007-11-17 16:19:28AdamChlipalaNo more domtool.deleuze122007-11-14 14:56:59MichaelOlsonPoint to Examples page, remove "brag on domtool" line112007-11-14 14:53:48MichaelOlson102007-11-14 14:53:22MichaelOlsonClarify by mentioning copying92007-11-14 14:51:39MichaelOlsonAdd warning about testing domtool configuration82007-11-12 01:13:35MichaelOlsonAdd domtool.deleuze to instructions72007-11-10 00:14:41AdamChlipalaIP address comment62007-11-08 20:38:01MichaelOlsonAdd hcoop-specific instructions52007-10-28 01:48:58MichaelOlsonAdd rmdir42007-10-28 01:46:21MichaelOlsonWrite page32007-10-27 19:19:21AdamChlipalaMention changes to DomTool/UserGuide22007-10-27 17:51:32AdamChlipalaComments12007-10-25 00:07:09MichaelOlsonInitial contentsThis is the chapter of the MemberManual that describes the bare minimum that you need to know concerning our use of DomTool. This is meant to be a very brief HCoop-specific overview, compared to the DomTool/UserGuide page, which is more thorough.

Domtool has user-specified configuration files that determine how to set up a domain or subdomain. Each file contains all of the information needed to configure a single domain. If you want Domtool to process these files automatically, then place them in the ~/.domtool directory. If you are just testing out a domain temporarily, the configuration files may be placed anywhere. By default, this ~/.domtool directory is actually a symlink to the ~/.public/.domtool directory. This makes your configuration files readable by anyone, but writable only by you. If you want to make them private, then do the following.

In order to activate or test a domain, you must run the domtool command. It can take a long time to run, like many minutes, so have patience.

Running the following command tests your configuration file (here called "MYDOMAIN") for errors. Make sure to give the full path to the configuration file, unless you are currently in the same directory as the configuration file. The "-tc" argument means "type-check". It is highly recommended to store your domtool configuration in a different directory while you are testing it (for example, ~/.domtool-test). The reason for this is that admins sometimes need to regenerate all domtool configuration files, and if any of your files in ~/.domtool have errors, none of them will be published. Once you are done testing, copy the known-good configuration files to ~/.domtool.

In order to make your changes go live, you need to run domtool without the "-tc" argument, as follows.

The intention of this page was to give you a very quick overview of the domtool command. To learn about how to create working configuration files, it is essential that you read the Domtool User Guide, and also see some examples. CategoryMemberManual