Unable to load self-built webadmin

[jeremiah]

I've downloaded and built webadmin with trunk. I've uploaded the built webadmin.zip file to my server and I think successfully configured through the existing webadmin the correct path and location of the zip file to update with my binary.

However it does not get loaded, despite restart. I note a warning in the logs;

2025-08-29T14:11:25Z INFO Webadmin resource unpacked (resource.webadmin-unpacked) path = "/srv/mail/etc/STALWART_WEBADMIN"
2025-08-29T14:11:25Z WARN Configuration build warning (config.build-warning) details = "WARNING for "webadmin.resource": Database key defined in local configuration, this might cause issues. See https://stalw.art/docs/configuration/overview/#local-and-database-settings"

Reading that file seems to imply that there is a key in the blob database that I have to change? Is that correct and, if yes, how do I do that?

[stappersg]

On Fri, Aug 29, 2025 at 07:27:06AM -0700, Jeremiah C. Foster wrote:

I've downloaded and built webadmin with trunk. I've uploaded the built webadmin.zip file to my server and I think successfully configured through the existing webadmin the correct path and location of the zip file to update with my binary.

However it does not get loaded, despite restart.

For such tests did I rotate the favicons. ( https://salsa.debian.org/debian/stalwart-webadmin/-/commit/d355c59f5cbb2beafcb4ee40b48652cd56f8ef0e )

I note a warning in the logs; 2025-08-29T14:11:25Z WARN Configuration build warning (config.build-warning) details = "WARNING for "webadmin.resource": Database key defined in local configuration, this might cause issues. See https://stalw.art/docs/configuration/overview/#local-and-database-settings"

https://github.com/stalwartlabs/webadmin/issues/100#issuecomment-3221448641 reports the same warning.

Reading that file seems to imply that there is a key in the blob database that I have to change?

The warning about "local setting and database setting" in my words:

Key "foo" is set at two places, both places are valid.
Which setting wins, is undefined behaviour.
Please unset "foo" at one place.

Is that correct and, if yes, how do I do that?

:-)

This issue is IMNSHO for git repo stalwartlabs/stalwart, not for this git repository.

Those who want to report it over there, please do.

Groeten Geert Stappers

P.S. My current workaround is https://salsa.debian.org/debian/stalwart/-/commit/ed309ab5f300dae9d6ca9b42640f62f9777f3b98

Silence is hard to parse