Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Andrew Patterson <apatterson@gitlab.com>

doc/maintenance/index.md

@@ -35,6 +35,36 @@ As a demonstration, the first line of the previous example can be interpreted as
 - `971` is the process identifier for the logging process.
 - The logging process has been running for 7 seconds (`7s`).
+## Show configuration
+
+Run `sudo gitlab-ctl show-config` to show the configuration that would be generated by `gitlab-ctl reconfigure`. The output is in JSON format and will look similar to this:
+
+```plaintext
+{
+  "gitlab": {
+    "gitlab_sshd": {
+
+    },
+    "gitlab_shell": {
+      "secret_token": "<SECRET_TOKEN>",
+      "auth_file": "/var/opt/gitlab/.ssh/authorized_keys"
+    },
+    "gitlab_rails": {
+      "smtp_address": "smtp.example.com",
+      "smtp_port": 587,
+      "smtp_user_name": "user@example.com",
+      "smtp_password": "<SMTP_PASSWORD>",
+      "smtp_domain": "smtp.example.com",
+      "smtp_authentication": "login",
+      "monitoring_whitelist": [
+        "127.0.0.0/8",
+        "::1/128",
+      ],
+   ...
+```
+
+After GitLab is reconfigured, you can look at the auto generated YAML configuration files under the `/var/opt/gitlab` directory for the corresponding service to check the latest configuration applied. In the example above, you can check the configuration for `gitlab-rails` under `/var/opt/gitlab/gitlab-rails/etc/gitlab.yml`.
+
 ## Tail process logs
 See [settings/logs.md.](../settings/logs.md)