• 4 Posts
  • 12 Comments
Joined 5 years ago
cake
Cake day: March 11th, 2021

help-circle

  • Well, it was officially and well supported before. It is just awfully complicated and unintuitive. So much that I decided to vibecode a GUI to manage my sharings with family members.

    Now that I did that, Radicale’s native sharing and permissions system makes more sense but is still unusable by most people in need of a simple sharing / editing / per user permission management.

    Here’s an example:

    <rights>
    [admin-root]
    user = user1
    collection = 
    permissions = R
    
    [admin-principal]
    user = user1
    collection = user1
    permissions = RrWw
    
    [admin-full]
    user = user1
    collection = user1/.*
    permissions = RrWw
    
    [admin-read-user2-root]
    user = user1
    collection = user2
    permissions = R
    
    [admin-read-user2-cal1]
    user = user1
    collection = user2/cal1
    permissions = Rr
    
    [admin-read-user2-cal2]
    user = user1
    collection = user2/cal2
    permissions = Rr
    
    [user2-root]
    user = user2
    collection = 
    permissions = R
    
    [user2-principal]
    user = user2
    collection = user2
    permissions = RrWw
    
    [user2-full]
    user = user2
    collection = user2/.*
    permissions = RrWw
    
    [user2-read-write-user1-cal3]
    user = user2
    collection = user1/cal3
    permissions = RrWw
    
    [user2-read-user1-cal4]
    user = user2
    collection = user1/cal4
    permissions = Rr
    
    [user2-read-user1-cal5]
    user = user2
    collection = user1/cal5
    permissions = Rr
    
    [user2-read-user1-cal6]
    user = user2
    collection = user1/cal6
    permissions = Rr
    

    For anyone curious about my vibecoded thingy, I just switched the repo to “public”. It’s in French, but can be instructive for anyone willing to understand more about how sharing and permissions work.

    As for Radicale v3.7, I’ll need to check what has changed. Thanks for sharing








  • Fair point about screenshots.

    Just to clarify though: I’m not the developer, I’m just someone who has been following the project for a while and wanted to give it a bit of visibility here because I think it’s promising.

    Since it’s still a young project, the README is understandably a bit rough around the edges. My post was mainly meant as a heads-up for people interested in self-hosted calendar tools, not as a finished product showcase.

    That said, constructive suggestions like adding screenshots are definitely useful, opening an issue, like @inari@pifed.zip did, or contributing to the README would probably help the project more than my post ever could 🙂