Abrechen2

joined 1 day ago
[–] Abrechen2@lemmy.world 2 points 20 hours ago (1 children)

No worrys , I didn’t understand it in a negative way. Just realized that tracking might be the wrong word to describe the use case of TravStats.

[–] Abrechen2@lemmy.world 2 points 1 day ago

To answer the second question: Currently it’s only for flights but there will be more like cruises and hotel tracking.

So if you not fly often it’s still worth in my opinion if you like statistics and stuff, if not than you don’t need something like this.

I am a frequent flyer and traveler for work and private. and I didn’t found a good way to display all my trips at once, so I started this.

[–] Abrechen2@lemmy.world 3 points 1 day ago (3 children)

Sry, like I explained in terabyterx comment, It’s not the traditional tracking, it’s to Collect flights and have statistics.

But Not only flights, next will be cruise and special flights. It’s more statistics, with Archivments

[–] Abrechen2@lemmy.world 2 points 1 day ago

I think you Brought up a good point, I think tracking is a bit misleading…. It’s more for collecting were you have been with statistics, a little bit like Google time line. The lists you can do in all the flight apps I know want correct input to display it or save it, but for example my very first flight , I don’t really have data from this one. As long do you have departure and arrival Airport you can add it to the List of your flights.

And the good part is, it’s all on your own server. So privacy is better for your personal data.

Thanks for bringing it up, I will rethink the tracking part in the texts

[–] Abrechen2@lemmy.world 2 points 1 day ago

Hey, I understand and see the Problems my Self in every Community with the AI Apps.

But this one is not a simple Vibecoded AI Shit, and I really try to get a really nice good working App.

And I stay on it, and want to do more. I am working currently on getting it to do Multi Domain Tracking, so not only flights.

But it’s your opinion, so feel free to ignor me… 😀

[–] Abrechen2@lemmy.world 7 points 1 day ago (1 children)

yes thats a possible way too.

[–] Abrechen2@lemmy.world 6 points 1 day ago (3 children)

Ahh, Okay i understand what you mean. I try of course to understand how everything in the app works. Most of comments tha start like your first end with lot of hate, beacause of the use of AI, thats why i am more carefull and a bit anti.

[–] Abrechen2@lemmy.world 17 points 1 day ago (5 children)

The core started as a personal tool I wrote by hand years ago — basic CRUD, my own flight list, ugly but mine. The polish, the visualisations, the parser, the multi-domain stuff, all the things that make it actually shareable — that's where AI assistance (Claude Code) kicked in. I drive the architecture and review every change; the AI does a lot of the typing. Without it I'd never have gotten this from "works on my machine" to "you can run it too".

One more thing: I have dyslexia, so all written text in the app, the docs and posts like this one gets cleaned up with AI help. That's not a workaround I'm hiding — it's the only reason the README is readable and the UI strings are consistent. Same principle as the code: I decide what it should say, the AI helps me say it clearly.

 

Hey r/selfhosted Lemmy crowd,

I built TravStats because I wanted to log my flights without handing my travel history to MyFlightradar24, App in the Air, or whatever SaaS-of-the-month. Started as a weekend project, has grown into something I actually use daily.

What it does

  • Booking email parser — drop your Lufthansa / BA / Berge & Meer / whatever confirmation mail in and it auto-fills the flight via local LLM (Ollama, gemma3:12b works great). No manually typing 200 flights.
  • 3D globe of all your routes (deck.gl + MapLibre), plus heatmap, hexagon, arc and time-slider modes — watch your flights build up over the years
  • Boarding pass scanner as a fallback (OCR) for the cases where you only have the PDF
  • Stats, achievements, certificates for the gamification fans
  • Cruise tracking with sea-route rendering (because flights aren't the only travel) (Comming Soon)
  • DE / EN UI

Stack

  • Single Docker image, Postgres sidecar
  • Node + TypeScript backend, React + Vite frontend
  • AGPL-3.0
  • Optional: Ollama on a separate box for the parser (CPU-only is fine, gemma3:12b on a Mac mini works)

Install

  • Unraid: in Community Apps, search "TravStats" → one-click
  • Anywhere else: docker compose up -d with the example compose file in the repo
  • No external account, no telemetry, JWT in HttpOnly cookies, secrets auto-generated on first boot

Links

Still actively developing — currently on v1.2.1. Happy about feedback, issues, feature requests. If you give it a spin and the parser eats your booking confirmation cleanly, I'd love to hear it; if it doesn't, even more so.