Skip to content
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

Display Rocket Chat Version Number #1111

Closed
MuhClaren opened this issue Oct 15, 2015 · 14 comments
Closed

Display Rocket Chat Version Number #1111

MuhClaren opened this issue Oct 15, 2015 · 14 comments

Comments

@MuhClaren
Copy link

Are there any plans to introduce a version number somewhere in the UI? It'd be greatly helpful to have at-a-glance the current version running. Takes the guess work out of wondering if it's the latest docker image or not. Thanks for considering this.

@andrewgdunn
Copy link

It'd be very nice to know version-build as I re-deploy via docker. I have noticed several things I'd like to have reported as issues, but I can't attribute them to a specific build without slogging through the docker build IDs.

@gmsecrieru
Copy link
Contributor

This should be possible with the efforts related to #961.

@geekgonecrazy
Copy link
Contributor

@MuhClaren I think this is very much the plan. We're working on our build flow. It should be available very soon.

@geekgonecrazy geekgonecrazy changed the title Feature Request: Rocket Chat Version Number Display Rocket Chat Version Number Oct 15, 2015
@Sing-Li
Copy link
Member

Sing-Li commented Oct 15, 2015

100% accurate.

@MuhClaren
Copy link
Author

A build number would be just as good; if it can be derived from the result of #961, that'd be excellent. Thanks for all your time and effort on this project. Cheers.

@Sing-Li
Copy link
Member

Sing-Li commented Oct 16, 2015

@MuhClaren thanks.

Every new build now includes a version + build number.

For now, it can be accessed directly via : http://<your server name>/buildinfo/buildinfo.txt

Starting today, we will not be supporting any vX.X.dev build officially (devs can still get great help from the community on our demo community server ).

Other tickets will be created to 'read and display' this version information in more UI/UX friendly way across clients and servers - including mobile, Electron, web, and so on.

Please track progress (and improve the doc) on this wiki page.

There is a minor bug #1117 which should be fixed shortly.

I am closing this case for now.

@Sing-Li Sing-Li closed this as completed Oct 16, 2015
@MuhClaren
Copy link
Author

Great work! Thanks!

@JackDragon
Copy link

I couldn't find information on this, but this url does not work anymore. Instead, you can go to <your server>/api/info instead now to view your version info.

Shailesh351 added a commit to Shailesh351/Rocket.Chat that referenced this issue Mar 14, 2022
@HoldOffHunger
Copy link

It's been almost a decade. Is there yet any plan to show a version number in Rocket chat?

@geekgonecrazy
Copy link
Contributor

image
has been here for a while

@HoldOffHunger
Copy link

not-working

How do you get to the "Info" page you're linking there? Because I have clicked every link in the top-left corner and nothing shows the version number. For example, I'm looking at: https://rchat.example.com/home . There is no version here at all.

@dudanogueira
Copy link
Contributor

@HoldOffHunger
If you are the ADMIN of that instance, you can go to your avatar, then ADMIN > INFO

If you are not... you can check under the API:

https://open.rocket.chat/api/info

@HoldOffHunger
Copy link

Oh, yeah, that works. But I mean, is there a way to just show the version number in the documentation/main/page/whatever page? It can't be hidden because it's a "security issue," if I can just look it up in the API.

Most applications show their version number in the doc/main/page/whatever page. So they don't have to have their sys admins hunt down version numbers and figure out whether an application is out of date or not. I don't see why this information isn't just displayed normally?

@joker234
Copy link

I also have the issues that I can't easily track the version number anymore and let my monitoring system notify me when it's time to update, because of #16050. Do I understand it correctly, that I have to give my tooling full admin API access (see also #16050 (comment)). I think it's more of a security issue if I use admin API tokens in to many tools than everyone being able to read the patch version ;) I searched (as @HoldOffHunger did) as well for documentation. Is there any?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants