Selfhosted

59121 readers

711 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Radicale v3.7 collection sharing? (github.com)

submitted 3 weeks ago by uuj8za@piefed.social to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

Looks like in Radicale 3.7, there is improved collection sharing? Has anyone tried using this?

I haven't tried any sharing previously because it seemed like it wasn't officially (or well) supported before, since you had to do some weird symlink hack.

Is sharing now more officially supported now? I looked at the UI, but I didn't see anything mentioning sharing...

you are viewing a single comment's thread
view the rest of the comments

[–] eszidiszi@lemmy.world 3 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

It's IMHO poorly documented (in terms of visibility).

Since it is not enabled by default, you have to edit your config file with the '[sharing]' section. There are two types, by map and token to conform to different usecases. There are also two different storage types, csv and files. Personally i chose map and csv way.

After adding your config and restarting the server, in the gui you can find a new button to share next to your calendar / carddav and in the bottom right menu an entry to accept invites issued by others.

I previously shared with the symlink too but since this update i got rid of it and used this new system and, well, it works for me (i'm sharing ro only calendar but you can assing [limited] permissions too).

[–] uuj8za@piefed.social 2 points 3 weeks ago (1 children)

There are two types, by map and token to conform to different usecases.

Ahh, ok... I'm seeing the docs.

ShareType: type of share

    token: token-based share (do not require user authentication)
    map: map-based share (requires user authentication)

Ahh, ok. So whether you need authentication or not.

There are also two different storage types, csv and files.

And the docs for that...

CSV

One CSV file containing one row per sharing config, separated by ; and containing header with columns from above.

If given, properties are stored in JSON format in CSV.
Files

File-based configuration store is using encoded PathOrToken as filename for each config. File contains the data stored as "dict" in binary Python "pickle" format (same is also used for item cache files).

So if you want plaintext vs binary storage.

you have to edit your config file with the ‘[sharing]’ section.

Would you mind sharing your config, pretty please. 🙏

[–] eszidiszi@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago)

Here is the relevant section:

[sharing]
type = csv
database_path = /var/lib/radicale/collections/sharing.csv
collection_by_map = true
permit_create_map = true

Just FYI, my filesystem_folder is defined as /var/lib/radicale/collections.

BTW. The token based sharing, as I understand, still requires auth, just not an user auth but, well, a token one.