26
CalDAV web gui (feddit.it)
submitted 3 months ago by Shimitar@feddit.it to c/selfhosted@lemmy.world

Hi, Using radicale since I switched from next cloud, using dav5x on android pretty nicely.

I was thinking about adding a web ui to access my calendars too from web... Any recommendations?

Radicale web ui only manages accounts and stuff, not the calendars contents.

all 11 comments
sorted by: hot top controversial new old
[-] taaz@biglemmowski.win 6 points 3 months ago
[-] lemmyvore@feddit.nl 4 points 3 months ago

SoGo is a monster, it's super hard to set up because it's an entire email stack. If you only want a calendar interface it's way too much.

[-] Shimitar@feddit.it 3 points 3 months ago

Interesting but seems way overkill....

[-] Tiritibambix@lemmy.ml 5 points 3 months ago

Been looking for a solid solution for a while and found these:

https://github.com/intri-in/manage-my-damn-life-nextjs

https://github.com/nibdo/bloben-app

I use bloben. It's not perfect but it works

[-] Shimitar@feddit.it 0 points 3 months ago
[-] Tiritibambix@lemmy.ml 2 points 3 months ago

I don't remember when I last tried it but for some reason I disliked it. Why dont you use it ?

[-] Shimitar@feddit.it 0 points 3 months ago

Just learned about its existence from your link... Its referred there.

[-] Tiritibambix@lemmy.ml 1 points 3 months ago

Let me.know what you think if you set it up

[-] Cyber@feddit.uk 2 points 3 months ago

Hmm, I'm in a very similar situation... I think a few people use the calendar in Thunderbird for example, but I don't use an email client.

What I've found that works well enough for me is the calendar in Vivaldi - I can see multiple calendars (ie other family members) Work, etc... so far it's done me well.

[-] lemmyvore@feddit.nl 1 points 3 months ago* (last edited 3 months ago)

I'm using InfCloud, it has support for events, tasks and contacts so it pairs perfectly with Radicale (which is also what I use). It doesn't look amazing I'll be honest and it lacks some features but it works fine.

Here's my docker compose:

services:
  infcloud:
    image: ckulka/infcloud:0.13.1
    container_name: infcloud
    depends_on:
      - php
    ports:
      - "5233:80/tcp"
    volumes:
      - "infcloud:/usr/share/nginx/infcloud"
      - "./data/config.js:/usr/share/nginx/infcloud/config.js:ro"
    restart: always
  php:
    image: php:7.3-fpm-alpine
    container_name: infcloud-php
    volumes:
      - "infcloud:/usr/share/nginx/infcloud:ro"
    restart: always

volumes:
  infcloud:

Run it without mapping config.js first and copy it from the container, edit it on the host, then map the volume and reprovision the container. You have to find the section globalNetworkCheckSettings and add a href: entry that points to your radicale host, for example href: "http://192.168.1.1:5232".

Another essential setting is to edit the Radicale config file and add the following section:

[headers]
Access-Control-Allow-Origin = http://192.168.1.1:5233
Access-Control-Allow-Methods = GET, POST, OPTIONS, PROPFIND, PROPPATCH, REPORT, PUT, MOVE, DELETE, LOCK, UNLOCK
Access-Control-Allow-Headers = User-Agent, Authorization, Content-type, Depth, If-match, If-None-Match, Lock-Token, Timeout, Destination, Overwrite, Prefer, X
Access-Control-Expose-Headers = Etag, Preference-Applied

The -Allow-Origin host and port must match the URL where you access InfCloud in the browser.

If you use a reverse proxy and you put Radicale / InfCloud behind domain names you can use the domain names in config.js and config. As long as InfCloud knows where to find Radicale, and Radicale knows where InfCloud comes.

this post was submitted on 27 Apr 2024
26 points (84.2% liked)

Selfhosted

38652 readers
321 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS