Closed dantefromhell closed 2 weeks ago
Closing as this is not a bug. Stalwart needs write access to the configuration file if you use the webadmin or if not all required settings are present. When you use the minimal configuration Stalwart is trying to update the configuration file with the defaults to some of the missing settings. See this file for details.
What happened?
When deploying stalwart on NixOS the configuration ends may end up in the "nix store" which is a location that is intentionally read-only for all users, including root.
How can we reproduce the problem?
Configure stalwart on NixOS with the Minimal configuration
Version
v0.8.x
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
Internal
What operating system are you using?
Linux
Relevant log output
On the management web interface value can (e.g. hostname) can be changed, but result in a HTTP/500 error and the following log entries occur:
Despite the HTTP/500 the web interface will display the updated hostname until the stalwart process is restarted.