EDIT- The issue is having is with “Authentication”. I haven’t made it past that step. Incorrectly said “addresses” on the original post.

Yo yo! Fairly new to making a change towards privacy. My brother gave me a raspberry pi 4 and I want to experiment with that before making a bigger change towards my other electronics. Rn I’m working on using radicale on the pi4 and I’m stuck because I can’t understand the technological language.

I’m trying to follow the tutorial on the radicale website but am getting stuck in the “addresses” authentication part. I can’t enter in anything Into the initial command prompt I used to create the radicale website. And when I make a new command prompt and enter that in nothing happens. I asked AI and it spits out an answer that isn’t dumbed down enough for me. Lemmy is my last hope before I try Reddit …

Tutorial link for clarity https://radicale.org/v3.html#tutorials

    • littleguy@lemmy.cif.suEnglish
      31·
      10 hours ago

      Don’t listen to this person.

      He’s part of a culture that can’t tolerate people doing things differently from him.

    • IsoKiero@sopuli.xyzEnglish
      12·
      17 hours ago

      You absolutely can run services without containers and when learning and trying things out I’d say it’s even preferable. Docker is a whole another beast to manage and has a learning curve of it’s own.

      Containers can of course be useful but setting everything up, configuring networking, managing possible integrations with other components (for example authentication via LDAP) it’s often simpler just to run the thing “in traditional way”. With radicale you can just ‘apt install radicale’ (or whatever you’re using) and have a go with it without extra layer of stuff you need to learn before getting something out of the thing. And even on production setups it might be preferred approach to go with ‘bare metal’, but that depends on quite a few variables.

        • IsoKiero@sopuli.xyzEnglish
          2·
          7 hours ago

          Maybe easier to get anything runnin quickly. But it obfuscates a lot of things and creates additional layer of stuff which you need to then manage. Like few days ago there was discussion about how docker, by default, creates rules which bypass the “normal” INPUT rules on many (most?) implementations. And backup scenario is different, it’s not as straightforward to change configuration than with traditional daemon and it’s even more likely to accidentally delete your data as a whole.

          As I already said, docker has its uses, but when you’re messing around and learning a new system you first need to learn how to manage the ropes with docker and only after that you can mess around with the actual thing you’re interested of. And also what I personally don’t really like is the mindset that you can just throw something on a docker and leave it running without any concern which is often promoted with ‘quickstart’-type documentation.