Display web app source tree version in frontend #79

Merged
luca0N merged 3 commits from dev_client_tree_version into dev 2026-08-03 11:17:58 +00:00
Owner

Display the source tree version in the web app frontend to let users know if they're visiting an unstable version of Lanbassador.

Display the source tree version in the web app frontend to let users know if they're visiting an unstable version of Lanbassador.
luca0N self-assigned this 2026-07-30 23:33:28 +00:00
Add prepare command
All checks were successful
/ Test client (push) Successful in 57s
403ab3e6db
Create new `npm run` command to prepare the sources.  At this time, this
is only used to fetch the product version from the repository tree at
runtime.  This way, if someone clones the repository and deploys the web
app whilst checked out at a branch (as opposed to a tag), it will let
users know that the source tree may not be stable.

These changes do not modify the behavior of `ng`.  `npm run prepare`
must be manually called before publishing the app.  Git is required at
runtime, but a default value is used and the user is warned if it cannot
be found.
Display product tree version in footer
All checks were successful
/ Test client (push) Successful in 58s
1050e90552
Use the PRODUCT_TREE_VERSION constant to display it in the web app
client footer.
Author
Owner

One of the issues that the current changes made to this branch introduce is with respect to the web app Dockerfile. Because it is expected to run from the client directory, the .git repository is not copied to the container, preventing the prepare script from detecting the source tree version.

Although inelegant, a solution to this problem would be to build the web app client image from the root of the repository (instead of the client subdirectory).

One of the issues that the current changes made to this branch introduce is with respect to the web app Dockerfile. Because it is expected to run from the `client` directory, the `.git` repository is not copied to the container, preventing the prepare script from detecting the source tree version. Although inelegant, a solution to this problem would be to build the web app client image from the root of the repository (instead of the `client` subdirectory).
Update web app Dockerfile to include tree version
All checks were successful
/ Test client (push) Successful in 57s
ce4bda06b8
Update the web app client Dockerfile so that it correctly prepares the
source code to include the source tree version.  This commit achieves
this by modifying paths so that the `docker build' command is now
expected to run from the parent directory (the root of the repository
tree).  The prepare script is ran automatically.
Author
Owner

Dockerfile tested and confirmed working. Merging.

Dockerfile tested and confirmed working. Merging.
luca0N deleted branch dev_client_tree_version 2026-08-03 11:17:58 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
luca0N/lanbassador!79
No description provided.