I have feedback on the adsb image, but I can't its repo. So I'll put it here. With only a 1090 receiver, not a 978, my logs are clogged with this: Code: Jun 30 22:56:20 raspberrypi systemd[1]: tar1090-978.service: Service RestartSec=30s expired, scheduling restart. Jun 30 22:56:20 raspberrypi systemd[1]: tar1090-978.service: Scheduled restart job, restart counter is at 42. Jun 30 22:56:20 raspberrypi systemd[1]: Stopped tar1090-978 - compress dump1090 json data. Jun 30 22:56:20 raspberrypi systemd[1]: Started tar1090-978 - compress dump1090 json data. Jun 30 22:56:20 raspberrypi tar1090-978[10004]: runtime directory or source directory are not specified or not directories, fatal error! Jun 30 22:56:20 raspberrypi tar1090-978[10004]: minimal Syntax: bash tar1090.sh <runtime directory> <dump1090 source directory> Jun 30 22:56:20 raspberrypi tar1090-978[10004]: Syntax: bash tar1090.sh <runtime directory> <dump1090 source directory> <history interval> <history size> <chunk size> <enable 978 yes/no> <URL for 978 aircraft.json> <interval 978 is updated> Poking around I see in the systemd that it is passing those params, but neither /run/tar1090-978 nor /run/adsb-exchange-978 exist. Hence the error and flapping. I'd have expected that service to behave with the other 978 services. I disabled it locally, but it's a bigger problem than just my install. (is 'hardware' the correct cat for this? I couldn't decide)
More feedback: - It'd be nice if /var/www/html/index.htm linked to the MLAT status page. I don't see that the region is saved in the configuration, which means it's more difficult to do so, unfortunately. - the HTML tags in index.htm are .. incorrect. The `<a href..>` tag isn't self closing, e.g., `<a href.. />` is incorrect. I even checked with the W3 validator to make sure it wasn't a style thing. Likewise, the closure shouldn't be a self-closure (`<a/>`), it should be a closure (`</a>`). Thankfully modern browsers accomidate all of these.
Sure, I was hoping for some degree of user-oriented feedback like the local map, the local grafana, and the /myip/ endpoint, since the USER is embedded in the adsb-config.txt it's almost possible to provide a user-friendly link. I'm realizing, though, that verbosity or user-friendliness must not be a goal. I don't know why I'm trying.
It is a goal, we're just busy Most realistic place for a link at least to the correct zone is probably /myip. It could have a link like this: https://adsbx.org/sync/5A
There is no image build, it's basically just a one off that gets modified. Quite suboptimal but it's not my construction site and i don't have the intent to make / support an image build either.