I’ve been using Obsidian for my note taking for a little while and I love it. I love you can just do a quick [[[other note]]] and it will link to the other note. I love that the full thing is just in markdown files, so that I can have full control; even if Obsidian were to disappear.

The one thing that is a little frustrating for me is getting my notes synced between my desktop, laptop, and phone. I have tried using syncthing to just sync the markdown files directly and it worked pretty well. But, it seems a bit overkill on my phone. I think I’d rather move to a single server that I can connect them to and they can sync from there.

I have looked into a few plugins. I saw that there a git one. I am a developer. So, that seems like the natural way for me to do it. But, I also saw a post on reddit where they suggested webdav. Which might be closer to what I want. I don’t need it to be where I can type on two devices and have the stuff sync super fast or something. I just want to type my notes, close the app, and when I open it on a different device; I want it to have my latest notes ready for me.

What are you personally using for Obsidian? I’d love to hear from other people here. I don’t want to pay for Obsidian’s subscription service. I want to host it myself.

  • layzerjeyt@lemmy.dbzer0.comEnglish
    1·
    8 days ago

    sudo docker compose up

    OK, well that works enough to access the specified port and loads the webapp. So that’s cool. :) There’s a tcp error printed in the page itself but ?maybe? that is caused by improperly running it.

    It could well be some self imposed error. But I’m always gonna be making those. If it is, it happened because I was trying to solve some other rudimentary issue. I’ve never gotten anything functional with this so it’s not like I was trying to do something fancy and got in over my head.

    Part of the issue with docker in this attempt and other times is it doesn’t give good enough errors/output to diagnose. It’s really kind of you to help me here but I can’t call you every step. The documentation is too focused on making things look simple even when they’re not, and therefor glossing over whatever system weirdies are getting in the way. You identified a user issue and even I suspected it (that’s why I tried all those commands with and without sudo in the above comment). Yet it is not in the official documentation as a potential cause of said error. And now that I have confirmed it, I have no idea how to solve it. I see in my browser history I’ve previously looked up “rootless mode”. Maybe that’s how I screwed this up in the first place.

    Moral of the story is, docker becomes a mess immediately. :D