It virtualises only parts of operating system (namely processes and network namespaces with ability to passthru devices and mount points). It is still using host kernel, for example.
It virtualises only parts of operating system (namely processes and network namespaces with ability to passthru devices and mount points). It is still using host kernel, for example.
Vikunja is the only viable thing. CalDAV spec allows to assign tasks, but we got XMPP moment here - spec exists, but almost no apps implement it properly.
Also you may take a look at https://github.com/awesome-selfhosted/awesome-selfhosted#task-management--to-do-lists
Syncthing is a sync utility wich is different from a cloud service. They both have different purpose and are for different tasks.
They all do one thing - syncing files. And less painful implementation done by nextcloud, at least for me.
I’m using nextcloud for files and photos/videos sync from mobile, Joplin for notes and tasks, baikal for calendar (with sharing with my wife which using iOS/macOS).
There is nothing better than Nextcloud for files, I was trying to use syncthing and seafile - both sucks in one way or another.
Also, I was using vikunja for tasks but it’s UI and UX… Well, strange and not eye-candy. I hope someday they’ll rewrite it.
I never said that it is a virtualization. Yet for easy understanding I named created namespaces “virtualized”. Here I mean “virtualized” = “isolated”. Systemd able to do that with every process btw.
Also, some “smart individuals” called comtainerization as type 3 hypervisors, that makes me laugh so hard :)