Selfhosted

60177 readers

573 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Safest CalDAV/CardDAV server [Choice Made] (feddit.org)

submitted 1 year ago* (last edited 1 year ago) by A_norny_mousse@feddit.org to c/selfhosted@lemmy.world

24 comments fedilink hide all child comments

After my previous server got hacked (presumably), I am now looking for new solutions to my needs. CalDAV/CardDAV is a big one.

So far I switched from a content management system (PHP) to a static site generator for my blog, and I'm not looking back.

I wonder if it makes sense to also step away from PHP wrt CalDAV/CardDAV.

As ever so often, this list has some nice info.

I'd like to keep dependencies low. Python would be a good choice because it's already installed on my Debian Stable system. But would it be safer?

Back when I started this compatibility with clients was an issue; but I don't use Android anymore. In any case, is this still an issue?

edit: no, I don't use a web based app; and I'd prefer the server doesn't require admin via web UI either.

Thanks for all your replies! I chose Radicale, already set it up. Only what is needed, simple config files. Very nice. It runs under an nginx reverse proxy and they communicate encrypted (and of course the outside is also encrypted and password-protected). And the web UI can be disabled.

The documentation is very tutorial-like and security conscious.

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

[–] non_burglar@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

I'm not sure what gave you the impression I don't follow the official procedure, I do follow the official upgrade procedure, and always have through its many stupid iterations for the last 8 years.

Example error, from last week:

Devs did not test with NC instances created before v21.x, so the SQL db is broken when going through the official upgrade if your nc has the old structure and I had to manually modify the actual db to work.

This kind of shit happens about twice a year. Mind you, this exact literal thing happened from v18.x to 19.x also, you'd think they has learned their lesson.

And php itself is fine. Not the most secure way to build a webapp, but fine. However, upgrading PHP on various platforms is an exercise in pulling your hair out.

Nextcloud is great when it's working. Most upgrades are fine. But when it poops the bed, it's another hour I can't get back. No other self-hosted software in my stack is like that.

[–] suzune@ani.social 1 points 1 year ago (1 children)

So you seriously expect an upgrade from major version 20 or less to major version 31 going well?

It's like upgrading from Windows 3.1 to Windows 11.

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

You misread that.

The database was from prior to 21.x, because i installed NC 8 years ago at v14 and have upgraded since then. I've been upgrading the same system since late 2016.

Stop picking fights with strangers.

[–] suzune@ani.social 1 points 1 year ago

No I didn't. You should really read the upgrade guide:

You cannot skip major releases.