Oh cool, this looks like something I’d really like. I’ve been using a paid Android app called Simply Auto which is excellent, but self hosting is more fun.

Does this work with all insurance again? I think it stopped working for instances on 0.19.4 and higher last I heard.

Cool, nice.

A reverse proxy needs you to forward ports 80 and 443, unfortunately.

At the bottom of the page (in a browser)

At the bottom of the page (in a browser) click ModLog and search for your username.

Cool!

“Easy” might just be relevant to your experience. You can follow along with the Ansible instructions, or go your own way with Docker and Docker Compose.

Both methods require a bit of work to get spun up, but it’s not too bad.

I’ve used it plenty of times for other reasons. I can never remember what kind of CPU I have and it tells me. I can’t even remember how much RAM I have, and it tells me that, too.

I’m sure the next thing someone is going to do is tell me the individual commands to find that info, but I can’t be bothered with that.

Oh thanks for the heads up

What’s this about?

Aha, that must be it. The photo in question is 6.7MB

I’m able to save a trail without any photos, but if I try to add a photo it lets me select the photo, but saving the trail gives a toast notification in the bottom right that says “Error saving trail.” The web, db, and search logs don’t show any errors.

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.

I just had another idea what the problem could be. I’ll ping you in the matrix chat.

Looks cool. I have it up and running with the docker compose provided. Every time I try to create a user it says “Error creating user”, and the logs say [ERROR] [23:30:00]: Login failed. Unable to obtain cookie.

Edit: I got it working, just had to updated some of the network stuff in the docker compose. The networking in Portainer is a bit “complex”.

I can’t get photos to work. Oh well.

I wouldn’t say so. Digital rights, online privacy, etc. apply to everyone, not just people sharing files on the internet.

Interesting choice.

Is Pirate Party a nickname or do they actually call themselves that?

This is honestly the most confusing and complicated part of self-hosting.

I agree! It took me years to finally decide to buckle down and wrap my head around what a “reverse proxy” is. Once I figured it out things became so much more usable and fun.

Combined with DNS redirects in my LAN (to get around NAT loopback), things are very easy to use.