-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Version Tag to Footer #427
Comments
for end user, important thing is to know
|
I think just using the docker image tag should theoretically work, since you're usually running docat with a version like |
We could/should show it at least on the |
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
That didn't work on the github pipeline (where it seems like the commit hash is used as a tag), so I just resorted to using the tag if present and the short hash if not. |
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the commit hash (if dirty) in the Footer. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the last tag + the number of commits since + the current hash (if dirty) in the Footer. Also added the Footer to the Help page. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the last tag + the number of commits since + the current hash (if dirty) in the Footer. Also added the Footer to the Help page. Fixes: #427
This currently uses an environment variable (`VITE_DOCAT_VERSION`) to display either the tag (if clean) or the last tag + the number of commits since + the current hash (if dirty) in the Footer. Also added the Footer to the Help page. Fixes: #427
It would be useful for auto-deployed systems if the current release / the current docker hash would be displayed in the footer or somewhere else so one can easily verify whether a new version has been published already.
The text was updated successfully, but these errors were encountered: