show how to configure cockpit

_toc.yml

@@ -80,6 +80,7 @@ chapters:
               - file: admin-guide/configuration/software/flatpak_remotes
               - file: admin-guide/configuration/software/python
               - file: admin-guide/configuration/software/conda
+              - file: admin-guide/configuration/software/cockpit
               - file: admin-guide/configuration/software/labview
               - file: admin-guide/configuration/software/citrix_vda
           - file: admin-guide/configuration/files

admin-guide/configuration/software/cockpit.md

@@ -0,0 +1,28 @@
+# Cockpit
+
+The Hiera example below will install and activate the [web based management interface Cockpit](https://cockpit-project.org/) plus eventually some required modules:
+
+```
+base::package_groups:
+  - 'cockpit'
+
+base::pkg_group::cockpit:
+  - 'cockpit'
+  - 'cockpit-...'
+
+base::sockets:
+  cockpit:
+    enable: true
+```
+
+If you would like to disallow access from externally and only allow connections from the host itself, then extend the socket configuration as below:
+
+```
+base::sockets:
+  cockpit:
+    enable: true
+    dropin: true
+    options:
+      Socket:
+        ListenStream: ['', '[::1]:9090']
+```

admin-guide/configuration/software/services.md

@@ -22,6 +22,16 @@ base::services:
         enable: false
 ```
 
+## Manage a Socket Activated Service
+
+For socket activated services use in Hiera `base:sockets` instead:
+
+```
+base::sockets:
+  cockpit:
+    enable: true
+```
+
 ## Manage Services with Custom Unit Files
 
 It is also possible to provide a full systemd unit file if there is none already. For this define the different secions and their content with subkeys below the `options` key as in below example: