That sounds good.

I added requests on Github for both of your points. The second one will be added, on the first one I need to check how much benefit we get out of it. It would improve the onboarding a lot, but then this is only a one time task.

Thank you for the feedback. I really appreciate that.

Let me know how it went. Only had an iPhone laying around to test it for a couple of minutes. Overland seems to be a really nice app. Shame the android version is non existing anymore

I just released v2.3.0 with Overland support. Thank you for the hint :)

Reordering Memories will make it into the next version after I have put some thoughts into it.

Hi @skbo@lu.skbo.net,

thank you for the feedback.

1. No, not right now. But this is a good point to add some form of sorting to the overview. I will create a request for it
2. Also not right now. But let me add a new integration to reitti. This seems like a reasonable choice. And the more we support, the easier it is to onboard new users.

Glad I could help and thank you for your feedback.

Hi Sunny, that is something reitti does not support. It heavily depends on the tracking.

Now, that I finished the memories feature i will add metadata to our Visits and Trips. With this, i have the idea to further enhance the Memories. So, you could tag certain Visits and Trips with data. But not right now.

Sure, in the Readme you can find a section how to run it from source. It is also possible to just take the app.jar from the release, put a file called application.properties with the needed settings besides it. Then run it with java -jar app.jar

That should work. I will add a section to the documentation for it. If you need any help, let me know.

Yes, this is supported

Hello Ada, since you are one of the first users it could be that at one point at the migration to a new version there was a hiccup. Did you used the older way over the shared instances feature or always the newer feature “Share with user”?

To fix this, you can take a look under “Share with user” and take note in the “Shared with you” section. There should only be one per shared user. Further take a look under “Integrations > Shared Instances” if there is also sharing setup. They both do the same but technically different.

This could explain why you are seeing them multiple times. Let me know if this helped, else we will sort this out somehow

Thanks for testing that. It never occurred to me during development. I will investigate what the issue could be.

Thanks a lot 🙏

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

Hi @themadcodger@kbin.earth, thanks for opening the discussion on https://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

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

Thank you 🙏

There is an integration for that. You provide the URL, the user and deviceId and Reitti will fetch all new data. There is also a button to import all historical data from the recorder

Hello @chellomere@lemmy.world , totally understandable point. I stated on another thread that I probably won’t add an export function since we discard some points of the raw data before Reitti processes it. So even if I add an export function, it will be less than the original data.

Some solutions to your problem could be:

• post your points into dawarich and update Reitti by hand using the GPX import. That is actually the way I did it in the beginning of development. GPX logger also saves the GPX files on your phone if you use that.
• another user pointed me to the owntracks recorder. Your data would be stored there and Reitti can be attached to the recorder. If there is a integration in dawarich, this could solve your problem for updating two apps.

I also considered writing a proxy like you mentioned which could delegate to two endpoints but then decided at one point it would not be worth the hassle. I stopped using dawarich but I am also biased 😅

If you are running Reitti with Docker, you can set the environment variable DANGEROUS_LIFE to true. This will enable a new section in the Settings. There, you can use the button ‘Clear and Reprocess’. This will delete all visits and trips and set all raw data points to unprocessed. During the next run, everything will be recalculated. In that settings section, you could also press the ‘Start Processing’ button if you don’t want to wait. Make sure to wait until the success message appears. It can take a while until all data is deleted and switched to unprocessed.