Add a env variable during compilation or something similar for packaging hints? (E.g. listed in support string)

[dionysius]

I wonder if its helpful for you if dowstream packagers could add a hint which would be shown in the support string? So you could quickly identify what type of compliation/installation or whether from your docker image an issue is coming from?

I played around with it a while ago here dionysius/vaultwarden-deb#43 but I rather like to discuss this with you first whether this is an idea you like or not.

Example:

* Vaultwarden version: v1.37.2
* Web-vault version: v2025.8.0
* Package: dionysius/vaultwarden-deb (trixie)
* Distribution: Debian GNU/Linux 13 (trixie)
...

[BlackDex]

You already are able to override the version if you want. You just need to be sure to use the same version numbers of course.
If you set VW_VERSION before cargo build it will use that string.

[BlackDex]

And, if you want to make it more deterministic, you can also add the git commit hash of course, that would make it more clear which specific hash you used.

[dionysius]

don't we run into dani-garcia/bw_web_builds#203 again if anything gets added to the VW_VERSION string?

[BlackDex]

It will work, as long as you also add the correct git hash, and we do not merge anything to main hehe.

VW_VERSION="1.37.5-28649978 [dionysius/vaultwarden-deb]"

But, once the sha changes, it will break again.
Maybe adding an extra env which we could check, and append to the version like i did here between [ ] isn't a bad idea.

[dionysius]

i'm not aware of many cases which were issues of my packaging. Can't say about how many there are for others. If you feel like its not worth (yet), no need to change anything - I'm happy to keep it the way it is.