369
I updated wanderer (v0.6.1) - a self-hosted trail and GPS track database (lemmy.world)
submitted 4 months ago* (last edited 4 months ago) by get_flomped@lemmy.world to c/selfhosted@lemmy.world
36 comments fedilink hide all child comments

Hey there,

it's been a while since my last post. Since then - with the help of this awesome community - I have added multiple new features and fixed a lot of bugs.

Most importantly there is now a working demo alongside a shiny new landing page.

And here are some more fun features I added since then:

  • Trail drawing: in addition to uploading you GPX, TCX or KML files, you can now also simply draw a trail by defining multiple waypoints. The route between them will be calculated automatically.
  • Sharing trails: simple and straightforward - you can share your trails with other users and let them view or edit.
  • Printing trails: there is now a dedicated print view. Plan your adventure digitally and then take it with you on paper.
  • wanderer is now available in 8 different languages (thanks to translators from the community). If you would like to contribute a translation you can do so here.
  • You can now bulk upload multiple trails at once simply by putting them in a dedicated auto-upload folder

And much more. I'd be happy if you give it a try in case you haven't yet.

GitHub repo: https://github.com/Flomp/wanderer

you are viewing a single comment's thread
view the rest of the comments
[-] tuhriel@infosec.pub 2 points 4 months ago* (last edited 4 months ago)

having the same issue, could you give some infos what you changed in the network settings?

edit: hadn't updated the ORIGIN env correctly (only updated the port): classic case of RTFM

[-] walden@sub.wetshaving.social 2 points 4 months ago* (last edited 4 months ago)

Mine was having some weird problem with docker, I think it must be a docker bug. Basically it put the Wanderer stuff at the very bottom of the routes (running "sudo route" on Debian lists the routes). The last entry in the routes table needs to be eth0 or the equivalent so that stuff can loop back to the beginning of the list. At least that's my understanding.

So anyway, to get around that bug/limitation I had to create a static docker network which I called "wanderer-static" using docker network create --attachable -d bridge --subnet 172.28.0.0/16 --gateway 172.28.0.1 wanderer-static. Choose a subnet that's not being used already.

Then in the docker compose file, point everything at that network by:

Removing

 networks:
   wanderer:
     driver: bridge

Adding

networks:
  wanderer-static:
    external: true

And finally, pointing each service to that network. Under each service you should have:

    networks:
      - wanderer-static

I also had to update the ORIGIN and whatever else to http://wanderer-static:7000, etc.

this post was submitted on 11 Jun 2024
369 points (98.9% liked)

Selfhosted

39677 readers
558 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz