ultrahorizon / UH-VPN-Docs

Documentation, bug tracker and feature request system for UH VPN
https://docs.uh-vpn.com
8 stars 1 forks source link

QUESTION: Ensuring the latest UH-VPN version #46

Closed sunny75016 closed 4 years ago

sunny75016 commented 4 years ago

I notice today that the routine "apt update && apt upgrade" has updated the uh-vpn-server. However, there is an inconsistency and I cannot be sure that the latest version has been installed. The result of the apt list command is below. root@vpn:~# apt list uh-vpn-server Listing... Done uh-vpn-server/focal,now 1.2.0-3 all [installed] root@vpn:~#

Google search shows a version number 2.0.0 - but that is wrong and seems to relate to the documentation.

In short, it will be nice if you can help in ascertaining the version number. Perhaps a changelog page on the website or github will equally serve this purpose.

AnthonyWharton commented 4 years ago

Please could you format your command outputs as code listings. For help on this refer to GitHub documentation.

Could you please tell us where you saw 2.0.0?

You can always find the latest versions on our Launchpad PPA, which may be updated ahead of our documentation which should be updated shortly afterwards :)

jwsi commented 4 years ago

Hi @sunny75016,

To follow on from Anthony's reponse, you can also find the latest version from the command line by executing:

apt-cache policy uh-vpn-server

This will tell you what version is currently installed and if there is an update available.

If you can link us to the Google result then we can look into that in greater detail.

sunny75016 commented 4 years ago

Ok. Thanks. Your solution works. I am able to reproduce the version 2.0.0 in a Startpage result. See screen snip. uh-screenshot

AnthonyWharton commented 4 years ago

Ahh yes, you're just seeing the docs platform version number. This is generated by the Read the Docs engine that we use and matches our backend API version number. We'll remove this from the page title now.

All of our applications (client/server) have their own version numbers which are managed on their respective platforms. We'll look into making a page that documents the latest versions of each on the docs in future, however it's fairly safe to trust updates from our official channels (linked from the website/docs) as all of these require code signing in order to be published.