-
-
Notifications
You must be signed in to change notification settings - Fork 549
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
Version Info in non Docker Deployment #156
Comments
maybe save version number in the DB and do a migration with each release? |
would be an option .. but i fear that everything except tags or some kind of automation will lead to me forgetting to change the number. But i am sure that there is some way to automate this, maybe with an automated commit or so. |
...or what is with a file like XML or JSON with the version number and changelog in it. |
Would this entail that the version number is shown on |
it ran on dev for a while but is back on latest now. The system page should also not be visible for non superuser users (which i just fixed) although it does not contain any kind of sensitive data. |
Sorry, I don't fully understand your answer. What I would basically like to know is: "as a regular user, can I find out which version is running on |
ok now i understand:
generally speaking the hosted version (currently) always gets the latest release when its released or a few days after that. In the future there might be some kind of more stable branch that will get the latest update lets say 2-3 weeks after the main branch so that its generally more stable. But currently development is to fast/unstable to do this. |
the next version will include a version iformation page based on commit refs |
Since the version number is only packed in the image at release, deployments not using docker will not contain a version number.
The text was updated successfully, but these errors were encountered: