Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)D
Posts
4
Comments
71
Joined
2 yr. ago

  • I thought i removed the image header field for the time being. Let me fix this and have a new release.

  • Thank you for the report. I will create a an issue for this

  • Thanks again for the awesome feedback. Points 1 to 3 are adressed in https://github.com/dedicatedcode/reitti/releases/tag/v2.4.1

    For the QR Code, I am not decided right now since you still would have to need to login before getting the the data from the backend. So it would only cut out the open the url and navigate to settings right now.

    Yes, I see that it is cluttered atm. I will update that page in the future propably

  • Hi @SKBo, thank you for the hint with the auto configuration. Today I had a look and all three apps support it in a way or another. I added it to the v2.4.0 release. I am really excited about that feature and just wanted to say thank you for pointing this out.

  • 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 @[email protected],

    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.

  • Selfhosted @lemmy.world

    Reitti v2.0.0: Introducing Memories – Transforming Your Location Data into Personal Stories

    github.com /dedicatedcode/reitti/releases/tag/v2.0.0
  • Thanks a lot 🙏

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

  • Hi @[email protected], 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 🙏

  • Selfhosted @lemmy.world

    Reitti Update Progress v1.3.1

    github.com /dedicatedcode/reitti/releases
  • Selfhosted @lemmy.world

    Reitti (v1.1.0) Update: Family mode, faster processing, colors!

    github.com /dedicatedcode/reitti/releases
  • Selfhosted @lemmy.world

    Introducing reitti: a selfhosted alternative to Google Timeline

    github.com /dedicatedcode/reitti