Fixes #590 - Replace APP_RESTART_CMD by AUTO_SHUTDOWN

admin/console/zammad-settings.rst

@@ -3,6 +3,26 @@ Query and Set / Update Zammad Settings
 
 .. include:: /admin/console/missing-commands-ask-community.include.rst
 
+Auto Shutdown Setting
+---------------------
+
+Defines if an automatic shutdown of Zammad is performed
+when the the database has been changed
+(e.g. after custom attributes have been created in the
+:admin-docs:`object manager </system/objects.html>`).
+The underlying system (Systemd, Docker, Kubernetes) will then restart the
+processes/containers after this shutdown.
+
+Default: **true**
+
+Setting this to ``false`` might only make sense in very rare cases and you
+have to restart the Zammad services then manually.
+
+.. code-block:: ruby
+
+   >> Setting.set('auto_shutdown', 'true')
+
+
 Ticket_hook Setting
 -------------------
 

appendix/configure-env-vars.rst

@@ -38,18 +38,6 @@ Use these environment variables to configure Zammad's behavior at runtime.
 General Options
 ---------------
 
-APP_RESTART_CMD
-   The command Zammad will use to automatically restart the server
-   after :admin-docs:`changes have been made in the Object Manager </system/objects.html>`.
-   (*E.g.,* ``"systemctl restart zammad"``)
-
-   If this is undefined, you will have to restart manually
-   after making changes in the Object Manager. Please keep in mind that Zammad
-   runs as unprivileged user. This means that you have to allow the Zammad user
-   via e.g. ``sudoers`` to run the required restart command.
-
-   Default: **unset**
-
 GPG_PATH
    Defines the path to the GPG installation. This is only needed if you
    installed Zammad from Source, if you want to use different versions of PGP