OwnTracks allows you to keep track of your own location. You can build your private location diary or share it with your family and friends. OwnTracks is open-source and uses open protocols for communication so you can be sure your data stays secure and private.
I have some questions about this one. You mention at the top needing a swarm cluster with persistent shared storage. But isn’t /var/data/owntracks going to be a separate dir on each host? I ask because I’m in the process of moving my owntracks install from a single node vps behind traefik 1.6 to an on-site swarm cluster behind traefik v2. Are you using ceph or something to back this? And… Is the application able to handle multiple instances, or are you limiting it to a single node? BTW the code example you give above is a good starting point, but I had very good success by using http with it instead of mqtt, much better reliability from the phones, and you don’t need any ports beyond traefik 443. Also mqtt over WSS works well, and for both options you can do basic auth + forward auth, and the user name is passed right into the owntracks data from the forward headers. I haven’t tried yet with oauth, but from what I can tell, yes, the oauth username will be passed to owntracks. I’m not sure it OT will be able to deal with the @ coming through into the username field… We shall see
I agree, HTTP is much simpler. I’m not sure it was available in OwnTracks when I was first playing with MQTT, but it’s by far preferable now. Yes, all the recipes assume that /var/data/<whatever> is on some sort of shared storage, be that Ceph, NFS, or something else.
FWIW, I stopped using OwnTracks when the HomeAssistant Companion app for iOS got advanced enough to handle location-reporting. (So that I can trigger various automations depending on whether I’m home or not)
D