Customising the public portal

[DJBenson]

Which part of the application does your idea belong to?

WebGui

Description

I have a use case which is probably well outside of the scope of the original project but I'd like to see if it's possible (by modifying the code locally) and whether it would be an idea for wider use.

I am hosting an instance of the tracker as a subdomain to a website related to our community broadband initiative. I want the public page to be accessable to all (which it currently is) but I'd like to modify it such that;

• There is some information about the page and links to the broadband provider
• The ability to hide the admin button (if the referrer is not on the local subnet maybe)

The second one is a nice to have but the first - is it possible to modify the code within the container to achieve this?

[svenvg93]

Technically you can by editing the dashboard.blade.php which is used for the Public Dashboard and mount it back into the container with a volume. Thats only to add text to it. There is no option to hide the admin button.

Would it not be easier to export the results to InfluxDB and build anpublic Grafana dashboard. There you can add a text block with the information and links you need.

[DJBenson]

Thanks for the advice - I've played with Grafana before and I'm rubbish at it but someone has built a dashboard already for speedtest-tracker (maybe one of the older / forks but it works nontheless).

Great idea and much better than what I was asking for.

Took a bit of working out because you cannot share a public dashboard without the user being able to get back to the grafana login and proxying the dashboard itself is difficult due to the websockets and dependencies it loads but I've managed it with;

• Alpine LXC container running docker
• Speed Test Tracker container
• Influxdb2 container
• Grafana container
• nginx container
• cloudflared binary

The user visits https://speed.mydomain.uk/ which goes via Cloudflare Tunnels to my LXC container, is terminated by nginx which proxies the request to grafana and also forces a redirect from the root to the dashboard which means the dashboard always opens by default and you can't (easily anyway) get to the Grafana login as that forces a redirect to the dashboard too.

Nice fun little project on a rainy Saturday in England.