RFE: Have the version number in the UI somehow reflect the date/time and SHA of the LibreBooking commit

[JohnVillalovos]

I was thinking it would be nice if at the bottom of the web page where it shows the LibreBooking version number if the date/time and SHA could be appended to the version number.

So for example right now it shows:

LibreBooking - GPLv3 v2.8.6.2

Would be nice if would show something like:

LibreBooking - GPLv3 v2.8.6.2-2025-06-24-0cd3ffee8

Maybe useful command:

git show --pretty="%cs-%h" --no-patch

[colisee]

Hi @JohnVillalovos,

I suppose you are referring to the dev-tagged docker image; right?

[JohnVillalovos]

Hi @JohnVillalovos,

I suppose you are referring to the dev-tagged docker image; right?

Yes. It would be nice if the dev-tagged docker image could show the SHA of the LibreBooking/app that was being used. No idea if that is difficult or easy...

[PierreSerpe]

Hi,
I m using develop as image version in docker-compose and was just wondering why 2.8.6.1 is displayed under the page.

[JohnVillalovos]

Hi, I m using develop as image version in docker-compose and was just wondering why 2.8.6.1 is displayed under the page.

Maybe you need to do a docker pull librebooking/librebooking:develop ?

[PierreSerpe]

Exact ! Thx

[colisee]

Bonjour @PierreSerpe,

since you are using a docker-compose.yml file, you can also run the docker-compose pull or docker compose pull command, depending on the docker version you are running.

Please, bear in mind that the librebooking/librebooking:develop image is rebuilt and pushed to the docker hub on a daily basis... If you are running librebooking in production, I would rather recommend you use a release version such as librebooking/librebooking:3.0.3.

[PierreSerpe]

Hi,

I have now 3.0.3 running in develop. Could it be a problem since the develop image is not pulled automatically from container manager on my synology nas?
I did try to start a production instance with docker-compose but i get an error at some stage related to the host.key

[colisee]

Which image is your container using: librebooking/librebooking:3.0.3 or librebooking/librebooking:develop ? In both case, refreshing the image is an action that is triggered from your NAS: either manuelly or via a scheduled job. Refreshing the :3.0.3 image on a daily basis does not make sense: may-be on a monthly basis, in order to grab the latest Debian updates... If you wish to continue this discussion, I would recommend you use discord. Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>

…

________________________________ De : PierreSerpe ***@***.***> Envoyé : Wednesday, July 23, 2025 1:39:01 PM À : LibreBooking/docker ***@***.***> Cc : Robin ALEXANDER ***@***.***>; Comment ***@***.***> Objet : Re: [LibreBooking/docker] RFE: Have the version number in the UI somehow reflect the date/time and SHA of the LibreBooking commit (Issue #101) [https://avatars.githubusercontent.com/u/102526566?s=20&v=4]PierreSerpe left a comment (LibreBooking/docker#101)<#101 (comment)> Hi, I have now 3.0.3 running in develop. Could it be a problem since the develop image is not pulled automatically from container manager on my synology nas? I did try to start a production instance with docker-compose but i get an error at some stage related to the host.key — Reply to this email directly, view it on GitHub<#101 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APKUZBJIAOZVWYZZ5ENGLYT3J5X5LAVCNFSM6AAAAACAAZUKT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMBXGM3DMMJUGQ>. You are receiving this because you commented.Message ID: ***@***.***>