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.

  • Nibodhika@lemmy.worldEnglish
    2·
    6 days ago

    I know you probably heard this thousands of times, but really, if you’re into self-hosting docker is a blessing. People make it harder than it needs to be when explaining all of the ins and outs. I assume you have a Linux box where you run your stuff, just install docker and docker compose there (you might need to enable the docker service, add your user to the docker group and reboot, unless you’re using a user friendly distro like Ubuntu). Then just make a folder anywhere for Silverbullet, create a file named compose.yaml and put the following text there:

    # services means that everything inside is a service to be deployed 
services:
  # this is the name of the service, you can put whatever you want
  silverbullet:
    # this is the docker image to use
    image: zefhemel/silverbullet
    # this is the rule to restart in case of crashes
    restart: unless-stopped
    # these are environment variables you want defined
    environment:
    # this is a specific variable for Silverbullet, it's essentially username:password change this accordingly 
    - SB_USER=admin:admin
    # volumes are local folders you want to be available
    volumes:
      # in this case we want that the folder ./space be mounted as /space inside the container
      - ./space:/space
    # these are the ports we want to expose
    ports:
      # This means expose port 3000 on port 3000, if you want to access Silverbullet on port 8080 this would be 8080:3000 (because internally the service is still listening to 3000)
      - 3000:3000

    Then run docker compose up and you should be able to access it on the port 3000.

    Ling story short docker compose looks for a file named compose.yaml in the local directory, and that file above has all of the information it needs to run the server. I’ve annotated each line there, feel free to remove the comments.

    • layzerjeyt@lemmy.dbzer0.comEnglish
      0·
      6 days ago

      I really appreciate the time you took to help me but seriously there is always issues even when it’s supposed to be simple/basic. Nevertheless I am in the mood to be wrong and pleasantly surprised so I follow your instructions. (Spoiler: It doesn’t work. But I am not trying to request further help about this, because I am fairly resigned to the situation. I am just showing you, that I tried.)

      I already had docker and docker-compose installed; I was already in the docker group; and the service was already active per systemctl. I guess from last time I tried this (not too long ago). Create directory, file etc.

      $ docker compose up
unable to get image 'zefhemel/silverbullet': Cannot connect to the Docker daemon at unix:///home/username/.docker/run/docker.sock. Is the docker daemon running?

      So I find Troubleshooting the Docker daemon | Docker Docs. It has several methods to find out if docker is even running which now I am confused about.

      reports as inactive: # systemctl is-active docker, # systemctl status docker.service, $ docker info

      report as active: $ systemctl status docker.service, # systemctl is-active docker,
      $ systemctl is-active docker, # docker info

      $ env | grep DOCKER_HOST and # env | grep DOCKER_HOST have no output.

      ps aux | grep docker and top | grep docker tell me dockerd is running by root. So I think maybe I need to start it as a regular user for this exercise?

      Found Start the daemon | Docker Docs which advises the use of dockerd either with or without sudo depending on environment.

      normal user:

      Starting up
dockerd needs to be started with root privileges. To run dockerd in rootless mode as an unprivileged user, see https://docs.docker.com/go/rootless/

      Oh it needs to be root. OK, try again with sudo:

      Starting up
failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 3952 is still running

      So it is running? 3952 was pid reported by top and ps. It is running. But it’s not running.

      Who knows… honestly this is how it goes every time. Maybe I am running services wrong… maybe I set something up last time because I was trying to solve another problem and it was suggested and that thing is now causing me am issue. I could chase my tail on this all week.

      Like I said I completely believe everyone that once you’re rolling with it, it’s great. I’m happy for everyone who is able to access this. I will continue to live without it for the time being.

      • Nibodhika@lemmy.worldEnglish
        1·
        6 days ago

        Wow, that’s very unfortunate. If you installed docker through package manager and have added yourself to the group I believe this to be self-imposed, I don’t know which mechanism Docker uses to give access to users in the group to its service, but seems related to that since it looks like the service is running but just your user can’t access it. To confirm it’s just that run the compose command as root, i.e. sudo docker compose up, this is not ideal but if that works you know it’s a permission problem with your user.

        You seem to know your way around Linux, so it’s probably not something obvious. I’m almost sure it’s something stupid and self imposed, I’ve done my fair share of stupid shit like leaving a config file malformatted or deleting a library or installing something through manually copying files only for something else to break because I overwrote something important.

        • layzerjeyt@lemmy.dbzer0.comEnglish
          1·
          6 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