Plan
Plan copied to clipboard
plan-player-analytics
Add support for server defined join address groups
I would like to be able to..
I would like if the server config could have predefined groups that can have user control visibility in addition to user adding there own
join_groups:
group_name: (show _ as a space in the UI)
"url/ip"
Is your feature request related to a problem? Please describe.
It very easy to lose groups and having some server defined ones give everyone viewing same data.
This has turned out to be surprisingly complicated since each server has its own join address list 🤔 I would assume server owner would like to configure all groups in one place on networks with multiple servers, but adding uuids to the config seems a bit cumbersome - and reusing one default group from the config for all servers doesn't seem to make sense
Yeah this kinda needs to be done. The Join Addresses page is basically useless if it doesn't remember what I'm trying to track. On top of that, it seems that I can't add more than one address into an "Address Group" in the page either.
On top of that, it seems that I can't add more than one address into an "Address Group" in the page either.
This has been solved in recent dev release. While selecting multiple is possible by holding down ctrl and clicking, it doesn't work on mobile and is unintuitive to users
That's good to know. Also for the implementation of the "defined address groups", would it not be possible to just store in the database which address groups the user is tracking? I personally don't think defining it in the config.yml is a good idea.
That's how it currently works if you have login enabled - The address groups you make are stored in user preferences.
When http only they are stored in browser local storage.
This ticket is more about having default values (or presets) for when you haven't created address groups
From what I can tell they wipe when I reload the page. I'm logged in as a user. I have reverse-proxied the webserver so maybe it thinks my instance is http-only? But I did follow the guide on Authentication with reverse-proxy.
Hmm, sounds like it could be a bug, I'll investigate when working on this ticket.
Should I make a bug-report somewhere else? I have a video I can submit of the bug taking place in case I might be doing something wrong.
https://github.com/user-attachments/assets/50ef2df0-73a4-41f2-856e-112a7a266cfd