Add current version details in the Web UI

[JinsoRaj]

I noticed the web UI doesn't currently show which version of Plausible is running. It would be really helpful to have this visible somewhere in the interface (perhaps in the admin / footer area).

This would make it easier to:

• Check the current version at a glance

• Know when updates are needed & to troubleshoot over updates

• Perform maintenance tasks

[aerosol]

You can try issuing a HTTP request to GET /api/system

[maxmorozoff]

Adding another voice in support of this feature request.

Beyond the practical reasons mentioned (checking version, updates, troubleshooting), having the version number visible in the web UI (and ideally, easily accessible info about the license and a link to the source code) is also very important for AGPL compliance for self-hosters.

The AGPL requires providing source code access to users interacting over the network. Including clear license information and a source code link directly in the application's interface helps self-hosters meet this obligation for their users effectively, especially when tied to the specific version.

This is particularly relevant in scenarios like mine: self-hosting an unmodified Plausible instance for a private client's use, integrated into their website. In such a setup, the client's administrators are users interacting with the software via the web UI. This raises the question of compliance: Am I fully compliant if the web UI itself doesn't provide easy access to the version number, license details, or a link to the source code for these users?

While other methods of providing the source might technically exist, making this information discoverable within the UI used by the client's administrators seems the most straightforward way to fulfill the AGPL's intent regarding providing access to network users in such private-use cases.

Making the version visible, as requested, would be a great step, and ideally, this section could also serve as the place to easily link to the source code, making AGPL compliance much simpler and clearer for everyone running Plausible.

So, +1 for this request, with the added context of license compliance being a significant benefit.

[maxmorozoff]

@aerosol Thanks for the suggestion regarding /api/system.

I tried querying that endpoint on a v2.1.4 instance, and the response I get shows the build information as null:

{"build":{"version":null,"created":null,"tags":null,"commit":null},"geo_database":"DBIP-Country-Lite"}

This seems to indicate that, at least in this older version, the specific build/version details aren't populated or available via that API endpoint.

So, while the API might provide other system information, this method doesn't easily solve the core problem highlighted in this issue: having the specific version number of the running instance readily visible within the web UI itself for quick checking and compliance purposes.