Reitti Update Progress v1.3.1

Reitti Update Progress v1.3.1 (github.com)
from danielgraf@discuss.tchncs.de to selfhosted@lemmy.world on 28 Aug 12:55
https://discuss.tchncs.de/post/43727497

After one month of development I want to present a short update on the progress of Reitti. We will start with a short introduction for the ones which do not know about it.

What is Reitti?

Reitti is a personal location tracking application designed to help users rediscover their movement patterns and revisit meaningful places from their past. The project focuses on transforming raw location data into accessible personal memories. As someone with aphantasia (inability to visualize memories), the Immich integration has been particularly valuable for me. Being able to see photos from specific locations and dates helps tremendously in reconstructing and remembering past experiences.

New Features

custom tiles server support added
added “Shared Instance” integration. This allows you to display the timeline data of other users. Even on other instances of Reitti. Perfect to connect with your friends and family. This feature supersedes the “Connected Accounts” feature and replaces it.
we have added OIDC Support to the login. You can now connect Reitti to your Provider and benefit from having to log in only once.
there is now a Live-Update Mode. This refreshes the map as soon as new data arrives
in companion to the Live-Update Mode, we also added full-screen functionality to have Reitti displayed in all its glory.
every user can now select his home location in the settings. This is used when displaying a day without any data.

Upcoming Features

Here are some ideas I will tackle next.

Replay Mode - Watch your day unfold step by step with animated playback of your movements
Long Distance Trip Enhancement - Improved UI specifically designed for viewing cross-country travels and extended journeys
Multi-Day Selection - Select and analyze patterns across multiple days simultaneously
Enhanced Statistics - Expanded stats section with more meaningful insights and fun discoveries about your movement patterns

Support & Community

Get Help:

IRC: irc.dedicatedcode.com

GitHub Issues: Open a new ticket for bugs or feature requests

Support the Project: ko-fi.com/danielgraf

Project Repository: github.com/dedicatedcode/reitti

Documentation: www.dedicatedcode.com/projects/reitti/overview/

I’d love to hear what you think.

Final words

I want to thank two new contributors since the last release for their effort on expanding and improving Reitti for everybody. Thanks a lot Elyviere and Terrance! 🙏

#selfhosted

threaded - newest

flightyhobler@lemmy.world on 28 Aug 13:03 next collapse

Looks great

danielgraf@discuss.tchncs.de on 28 Aug 15:41 collapse

Thank you 🙏

ReedReads@lemmy.zip on 28 Aug 15:09 next collapse

Great write up and thanks for explaining why you created it and also about the immich integration.

If it wasn’t for the immich integration I’d probably pass but I’m definitely gonna check it out now.

danielgraf@discuss.tchncs.de on 28 Aug 15:42 collapse

Thank you very much. Let me know if it fits your need or something is missing

themadcodger@kbin.earth on 29 Aug 00:29 next collapse

I love the integrations with immich and owntracks, as well as having an OIDC login. What kind of resources does this need for a server?

danielgraf@discuss.tchncs.de on 29 Aug 02:13 collapse

Hi @themadcodger@kbin.earth, thanks for opening the discussion on github.com/dedicatedcode/reitti/discussions/176.

As I mentioned there: It depends on your usage. Reitti on its own could probably run with 512MB of RAM. This would probably also work while ingesting data from one of the integrations. I doubt that imports of data, spanning more than one day, will work. We already stream the uploaded data but in the end, it has to go temporally into RAM. Either in Reitti itself or in Redis or in the DB.

For anyone interested. These are the numbers on my host for the stack idling and waiting for data.

ONTAINER ID   NAME                CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
222a0ed74fe7   reitti-reitti-1     0.10%     392MiB / 30.77GiB     1.24%     221MB / 103MB     2.11MB / 35.4MB   87
76c9317352bc   reitti-postgis-1    0.00%     83.38MiB / 30.77GiB   0.26%     67.7MB / 144MB    66.4MB / 145MB    16
06747b08882d   reitti-rabbitmq-1   0.46%     154.8MiB / 30.77GiB   0.49%     84.7MB / 91.3MB   46MB / 86.4MB     57
5012afdf4688   reitti-photon-1     0.42%     492.6MiB / 30.77GiB   1.56%     124kB / 5.51kB    616MB / 256MB     121
ddbc854a3940   reitti-redis-1      0.50%     4.875MiB / 30.77GiB   0.02%     52.2MB / 232MB    2.34MB / 164kB    6

Sunny@slrpnk.net on 29 Aug 06:40 next collapse

I am 100% checking this out!

danielgraf@discuss.tchncs.de on 29 Aug 08:23 collapse

Thank you. Would be nice to hear if it works for you or something is missing.

unskilled5117@feddit.org on 29 Aug 06:54 collapse

Very interesting project, especially the immich integration! Thank you.

danielgraf@discuss.tchncs.de on 29 Aug 08:23 collapse

Thanks a lot 🙏