Turbo Vision VS GoAccess

For those curious, here is a modern port of the C++ Turbo Vision that also supports Unicode:

https://github.com/magiblot/tvision

Not exactly what you're looking for, but there's Shell in a Box (see https://github.com/shellinabox/shellinabox), that can create a terminal on a web page, and expose an actual terminal application running on a server.

One thing that is certainly doable is also to use a standard TUI framework in another language (there are many of them, e.g. https://github.com/magiblot/tvision for C++, https://github.com/charmbracelet/bubbletea for Go, etc.), compile it to WASM, and find how to bridge the WASM output to the browser (I've seen this: https://github.com/cryptool-org/wasm-webterm, but never tried it).

With FPC, you can use Free Vision, which is a supposed to be like a remake of the old Borland Turbo Vision. Alternatively for C++.

Talking about a window display from byte array sounds like windowing for a purely text based (console based) user interface, like the 1990's Borland's old Turbo Vision. There are modern ports of Turbo Vision, e.g. superquick googling found one at GitHub.

there is also a port of the "original":

https://github.com/magiblot/tvision

A modern port of Turbo Vision 2.0, the classical framework for text-based user interfaces. Now cross-platform and with Unicode support.

I use https://goaccess.io/ to parse the logs and generate a html report.

As mentioned elsewhere in the thread, there is a lot of bot activity there, that using JS might cleanup a bit.

If you are interested, I have a write up of my setup here, with the report generation down at the bottom:

11. I use goaccess (https://goaccess.io) to look at my server logs and see what is hitting me.

GoAccess looks interesting; to be sincere, I haven't used it myself, but the demo website looks extremely fascinating to me! https://goaccess.io/

But how about if we want to analyze the access.log file as a single report? I found goaccess can help to the rescue. So here is how I used this tool to generate a report.

Goaccess (https://github.com/allinurl/goaccess) does this in real time and has been very stable for well over a decade.

GitHub: GoAccess GitHub Repository

Not forgotten by any means but goaccess is nice and simple to use

https://goaccess.io/

If one wants server-side metrics with a little more info than the author's "hacky little script", there's always goaccess [1], which functions in broadly the same way. I even use it with Firebase Hosting-hosted sites via [2] (which I wrote).

[1] http://goaccess.io/

[2] https://github.com/Silicon-Ally/gcp-clf

> Just use GoAcces for fuck's sake.

GoAccess seems pretty cool and is probably a good task for the job, when you need something simple, thanks for recommending it: https://goaccess.io/

Even if you have analytics of some sort already in place, I think it'd probably still be a nice idea to run GoAccess on your server, behind some additional auth, so you can check up on how the web servers are performing.

That said, I'd still say that the analytics solutions out there, especially self-hostable ones like Matomo, are quite nice and can have both UIs that are very easy to interact with for the average person (e.g. filtering data by date range, or by page/view that was interacted with), as well as have a plethora of different datasets: https://matomo.org/features/

I think it can be useful to have a look at what sorts of devices are mostly being used to interact with your site, what operating systems and browsers are in use, how people navigate through the site, where do they enter the site from and how they find it, what the front end performance is like, or even how your e-commerce site is doing, at a glance, in addition to seeing how this changes over time.

People have also said good things about Plausible Analytics as well: https://plausible.io/

Maybe, if it's just local and need just information, maybe https://goaccess.io is an option.