The configuration directory

All supervision trees are configured in their respective configuration directory.

• System supervision trees:
  /etc/goetia/system, which can be changed using the --sysconfdir=....
• User supervision trees: ${HOME}/.config/goetia/${USERTREE}, by default which can be changed using the --usrconfdir=@userconfdir@. @usrconfdir@ is prepended with ${HOME} and gets appended ${USERTREE}, resulting in: ${HOME}/@userconfdir@/${USERTREE}.

Thus, the structure shown below lies at /path/to/confdir=/etc/goety/system/ for system supervision trees. Since there can be an arbitrary amount of user supervision trees (per user), they are found at: /path/to/confdir=${HOME}/.config/goetia/@USERTREE1@, /path/to/confdir=${HOME}/.config/goetia/@USERTREE1@, etc.

All configuration directories are structured as follows:

/path/to/confdir
├── 1745932803_db
├── compiled -> 1745932803_db
├── env
├── run-image
│   └── service
│       ├── goetia-shutdown
│       ├── .s6-svscan
│       ├── s6-svscan-log
│       └── @SERVICEDIR1A@
└── src
    ├── @CATEGORY1@
    │   ├── @SOURCEDIR1A@
    │   └── @SOURCEDIR1B@
    ├── @CATEGORY2@
    └── @CATEGORY3@
		

These subdirectories have the following use:

• compiled
  is a symlink that points to the currently active database produced by the system-db command. The directory is used by init and commands like system-rc and their user supervision tree counterparts. Both compiled and 1745932803_db are autogenerated and need not be changed by anyone.
• env
  is an optional directory that contains environment variables in the envdir format. It is sourced by init before the invocation of s6-svscan and thereby the environment defined here is passed to all services.
• run-image
  is a directory from which all contents are copied to the runtime directory. The most important functionality of this is the run-image/service subdirectory, which may contain service directories. Service directories are different from source directories in that they are not managed by s6-rc. Once copied to the runtime directory, are directly recognized by s6-svscan, which in turn spawns s6-supervise. s6-supervise then interprets and starts the services defined in those service directories. All of this happens even before s6-rc-init is invoked, thus service directories are suitable for services that need to be available early and have no dependencies.
• src
  contains source directories for use by s6-rc. The source directories are dubbed @SOURCEDIR1A@, @SOURCEDIR1B@, ... here. These are categorized in directories that can be named however desired and are dubbed @CATEGORY1@, @CATEGORY2@, ... here. The purpose of these directories is to nicely organize the source directories.