For the last month or so I've been working on bewCloud, and today I'm making its source code public and open!<p>Right now, the Dashboard (URLs + freeform notes), News (RSS/Atom/JSON feeds), and Contacts (CardDav) are working.<p>If you have any suggestions, comments, or recommendations, I'd love to hear it.<p>Thank you for your attention and kindness. I really appreciate it!
Any reason this is all one giant project? One of Nextcloud's IMHO fatal mistakes is it tries to be everything. So people have to choose between say, a better todo app, or the one that's integrated with their monolith of choice.<p>Meanwhile, if you approach each module as it's own project, but with shared code where sensible, and open standards driving your integrations, people including you, can select the parts that best suit them while mixing in software from others where appropriate.
This looks cool. I don’t know what direction you’re going to take this, but my big challenge with Nextcloud is that the file syncing gets very unreliable in short order. I honestly would love to see someone do something like this with Syncthing as a file management backend. It is honestly the best tool of its kind, and it is extremely fast and reliable.
Really cool to see this I hope you're able to continue this work. As others have said, CalDAV / CardDAV are complex standards and getting the nuances right without using some tried/true libraries (sabre-dav) might be a challenge.<p>Two points:<p>For just CalDAV / CardDAV there's Radicale, Davical and Baïkal all of which work pretty well and are relatively easy to set up, so this might be a bit of wheel re-invention.<p>Perhaps you might consider relying on those projects for calendar / contact sync and then add your other pieces (file, photos, etc).<p>Second point is I think the reason why Nextcloud / Owncloud end up becoming super-slow for file sync is unfortunately the use of WebDAV.<p>I can't find the thread at the moment but I remember the developers from one of those projects saying that WebDAV itself makes the file-sync super slow and resource heavy.<p>As a result I think the Owncloud++ or their golang based re-implementation prefers the use of S3-compatible for backend file store.<p>I'm not saying you should use S3, but if you continue down the path with WebDAV for file-sync you might find it's resource heavy and slow as Nextcloud/Owncloud might be.
"bew is web in reverse, similar to how deno is node reversed. "<p>Deno is an anagram of node, not reversed :)<p>But looks nice, will have a look at it!
This could be great for homelabbers. I have around 40 services I run currently but every time I tried Next/owncloud I just removed it shortly after. Found it lacking speed, or resource consumption that was comparable to... the other 40 services combined etc.<p>This could perfectly fill that spot. Will be testing soon.
My biggest gripe is how often Nextcloud goes into maintenance mode. While this is currently slightly annoying, Nextcloud would quickly be rendered useless to my family would I pass away.<p>Please keep the upgrade process hands-off.
What libraries does your Contacts app use under the hood? I'm asking because pretty much every contacts app I've tried had countless bugs – either in CardDav or the vCard part (when importing/exporting) or both.