search

Crypter-File-Transfer / Crypter

A Blazor WASM web application that offers end-to-end encrypted file and message transfer using Libsodium, Entity Framework, Hangfire, Docker, NUnit, and Mailkit.
https://www.crypter.dev
GNU Affero General Public License v3.0
37 stars 15 forks source link

[Feature] Add version information to the web client #572

Open Jack-Edwards opened 1 year ago

Jack-Edwards commented 1 year ago

Description

I would like to know which version of the application I am using when I load www.crypter.dev.

Show the version number of the application somewhere on the front-end.

Good First Issue

This may be a good first issue for someone interested in ASP.NET and Blazor applications. This issue may also require some familiarity with Docker and/or Github actions.

Additional Comments

Truthfully, I'm not sure of the best way to accomplish this task. The release number isn't truly known until I publish a release in Github. The release is tagged and Docker images are uploaded to Github Container Repository (GHCR). You can see the Crypter.Web packages here https://github.com/Crypter-File-Transfer/Crypter/pkgs/container/crypter_web

Maybe we add a step in the release process that modifies the version number in the Crypter.web project's .csproj file? As in, perform a simple string replace.

Showing the version number in the application should be a simple matter of showing the assembly version from the code.

Jack-Edwards commented 1 year ago

I don't want to overload this issue too much, but keep in mind while working on the UI that we may also want to fetch and show the API version down the road.

Client version: 1.2.3 API version: 1.2.3

Ideally these numbers should always be the same, given the way our CI/CD is currently written. But it would be extremely useful to know when these numbers do not match. Did the API deploy fail? Is someone using a cached version of the web client?