Released version installed from source showing as "dev (dev, <TODAYS_DATE>)"

[burgerga]

Description

When downloading a specific release from the Github releases (e.g. by downloading https://github.com/gethomepage/homepage/archive/refs/tags/${RELEASE}.tar.gz) and building using
https://gethomepage.dev/installation/source/ I get this in my homepage:

after installation, however, I expected to see the version and revision I just downloaded from the Github Releases.
EDIT: this also prevents the update check

It would be nice if the release zip would include an .env file containing the required variables, like:

# NEXT_PUBLIC_BUILDTIME=
NEXT_PUBLIC_VERSION=
NEXT_PUBLIC_REVISION=

These will be automatically picked up by next (https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables#loading-environment-variables) and used for the build step. (I guess NEXT_PUBLIC_BUILDTIME can be omitted and filled in during the build step, or set to the date the release was made on Github)

homepage version

v0.9.13

Installation method

Source

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

Not relevant

[gabriellxxix]

I’m experiencing the same problem and would appreciate any insights or solutions if anyone has found a way to resolve this issue.

Thank you!

[burgerga]

I think you didn't use the relevant part (the exports before the build step):
https://github.com/community-scripts/ProxmoxVE/blob/main/ct/homepage.sh#L54-L57

[matkes]

@matkes For community-scripts this is now resolved with community-scripts/ProxmoxVE#1155 (just go to your homepage LXC and type update)

@burgerga Thanks! Unfortunately, the problem still persists after running the 'update'. Interestingly, when I created a new lxc container, the version was displayed.

[burgerga]

@gabriellxxix Ah make sure you use https://community-scripts.github.io/Proxmox/ and not the old tteck one (@matkes maybe this was your issue as well). You can bulk update your LXCs to the new repo using https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo

[matkes]

@gabriellxxix Ah make sure you use https://community-scripts.github.io/Proxmox/ and not the old tteck one (@matkes maybe this was your issue as well). You can bulk update your LXCs to the new repo using https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo

@burgerga
Big kudos to you for pointing this out! This in fact affects my other containers too. After updating from old tteck repository to community, running 'update' on homepage lxc finally displays version number. Big thanks for you, ttec's spirit is still alive.

[gabriellxxix]

Definitely, that's my mistake. I was using the old script and not the one from community-scripts... I'll test it now.