Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #590 - Replace APP_RESTART_CMD by AUTO_SHUTDOWN #591

Merged
merged 2 commits into from
Dec 17, 2024
Merged

Fixes #590 - Replace APP_RESTART_CMD by AUTO_SHUTDOWN #591

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bb9b04f
Replaced APP_RESTART_CMD by AUTO_SHUTDOWN
ralf401 Dec 16, 2024
30ee77d
Moved it from env variables to Console section
ralf401 Dec 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 11 additions & 9 deletions appendix/configure-env-vars.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,17 +38,19 @@ 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"``)
AUTO_SHUTDOWN
ralf401 marked this conversation as resolved.
Show resolved Hide resolved
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>`).

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.
The underlying system (Systemd, Docker, Kubernetes) will then restart the
processes/containers after this shutdown.

Default: **unset**
Setting this to ``false`` might only make sense in very rare cases and you
have to restart the Zammad services then manually.

Default: **true**

GPG_PATH
Defines the path to the GPG installation. This is only needed if you
Expand Down
Loading