4 ms·

Thanks for the great question! I think the main issue for me is I don't want to install and maintain multiple different services (contacts, calendar, tasks, fil

Thanks for the great question! I think the main issue for me is I don't want to install and maintain multiple different services (contacts, calendar, tasks, files, notes, photos, though arguably those could all "fit" in 2 services -- which is why I have two Nextcloud instances), and having a single service/server with those becomes easier to maintain. They all use open standards (CardDav, CalDav, WebDav), and that's why I can use DavX5 on Android and Gnome on Linux and Apple's default accounts/apps too. bewCloud has and will have a simple UI for each of those just because I think there's value to having an easy web access that's not sync-dependent. I hope that makes sense!

mrAssHat 3y ago
Why not have both? A single server/service AND easy-to-install modules providing atomic functionality? Just make the install/uninstall process easy (like just downloading and optionally unpacking a modules archive into installed_modules Dir)?
- jonwest 3y ago
  With the exception of a handful of core modules isn’t that exactly what Nextcloud does?
  - BrunoBernardino 3y ago
    Yes! Their "problem" is that they have to support a lot of legacy and extensibility, thus even just the "barebones" Nextcloud uses a lot of resources (CPU/Memory/IO).
- BrunoBernardino 3y ago
  Yes! Since these will be easy and used _as needed_, the plan is to have those be set by this `.env` var: https://github.com/bewcloud/bewcloud/blob/2d70a3817de1fd6108f625cb2b41398e77cd9813/.env.sample#L17 https://github.com/bewcloud/bewcloud/blob/2d70a3817de1fd6108... thus not requiring download/install/uninstall, but not bloat as they won't be used if they're not enabled.