[feature]: The frontend should show the current version of the frontend and the backend

[Aisuko]

I believe this feature is necessary. It will be easy for us deal with the specific issues which were happened in the specific version of code.

Frontend version

• We should follow the latest release version

Backend version

• We need to discuss if we need a new API to do this.

[cbh778899]

Perhaps there're some api to directly query from github, I need to have a look, will update in the future.

[Aisuko]

For the frontend, I think we should follow the release version. For the backend, we need to have a backend API to return the version of the backend.

[cbh778899]

I feels like split it would be kind of meaningless if we want to update dynamically, github do has APIs to query latest version, which needs an auth key for each end, so that one function passes the auth key (in deployment env variable) can do the work for both ends instead of call different functions, that might make the code less tidy.

[Aisuko]

Hi @cbh778899. We want to add version as a constant value inside the frontend and the backend. So, we can get these numbers easier. We don't get these versions from GitHub. Here is a scenario, after we deployed these containers. We open the frontend. And it will show the version of current deployed code.

[cbh778899]

Hi @cbh778899. We want to add version as a constant value inside the frontend and the backend. So, we can get these numbers easier. We don't get these versions from GitHub. Here is a scenario, after we deployed these containers. We open the frontend. And it will show the version of current deployed code.

good idea, simple & easy