Content
You are here:
Okay, the updating process is bad.
Added by Johannes Hass over 1 year ago
We're currently hosting OpenProject on a server on-premise. Every time I run apt update && apt upgrade
the server becomes unusable until I remember that I also have to do openproject configure
and then also putz around with the config file again because this process overwrites the config file without even asking.
Now, the way I remember updates going is that apt usually has a post-install hook which is explicitly intended for just such additional steps after installing/upgrading a module. Also, apt usually asks before overwriting a config file with default values.
Replies (2)
Hello,
Sorry for the bad experience. Could you let me know on which specific distribution you encounter the issue?
APT does indeed have a postinstall, but it cannot run ours because there may be additional packages to install depending on your configuration, and you cannot run apt within an apt postinstall.
Do you by any chance could pinpoint the settings that are overwritten? I’m assuming the database connection doesn’t get reset at any update, am I right?
Also, are you talking about the YAML configuration file, or the /etc/openproject/installer.dat file ?
Thank you for your help,
Cyril
We have the same issue with APT updates,
Hostname (despite having changed it in installer.dat) goes back to fqdn which breaks HAProxy, and any additional changes in the configuration.yml (we use Keycloak as OpenID provider) are erased.