Hi Martin, I just had a quick look at the docs for build Elm from source, and it looks like a pretty direct journey to npm hell. I'm pretty out of touch with modern web development, so I'm not sure how much help I can be be in terms of packaging Elm.
I can suggest a couple of alternatives. One would be to ship Alertmanager without any UI whatsoever, as has been done in the unofficial RPMs at https://packagecloud.io/prometheus-rpm/release. This obviously affects the end user experience quite substantially, but ultimately does not detract from Alertmanager's main functionality. The other option would be to bundle the necessary Elm libs with Alertmanager itself, but I suspect this violates Debian packaging policy. Even if somebody were able to package Elm and make it a dependency of the Alertmanager package, those JS libs need to somehow be served by the integrated web server in Alertmanager. I would normally expect to see an Apache or Nginx config snippet or .htaccess with some kind of directory alias, but obviously that won't fly in this case. Symlinks to directories? I don't think I've seen many (if any) Debian packages do that. Best, Daniel
