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

Thank you 🙏

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

No, not really. It just makes it easier to spin up all the needed services and it is at the moment the "documented" way.

On the release there is also jar of Reitti.

If you need any help in starting that, let me know.

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 😅

To change the password and the user of the db you have to change it in the postgis service but also need to let reitti know that it is not the standard anymore. You need to set the environment for reitti according to the Readme

If you want to start from scratch you probably need to delete the volumes from docker. See here

Normally the volumes are called reitti_postgis and so on.

Let me know if you need further assitance, i am currently on mobile but can provide more info later

You are right, I missed that they are still open for the other services. I have mine running behind traeffik and did removed all port definitions.

I will change the compose file to only expose Reitti.

Thanks for the feedback🙏

https://lemmy.zip/comment/19939541

Different focus

Reitti displays data coming either from an import. You could upload GPX, GeoJson files or export the data from google maps and import that. If you want more up to date data, you could install an app on your phone which pushes your latest locations into Reitti. GPSLogger or Owntracks are at the moment supported for that