atomic VS seaweedfs

Progress Update for Atomic's chat interface - https://github.com/rush86999/atomic

I'm trying to build an open source second brain for your calendar: https://github.com/rush86999/atomic . Would love some support with a star on the top right corner ⭐⭐⭐⭐⭐

Atomic's features are listed here: https://github.com/rush86999/atomic Thanks for reading Prompt list

Atomic's features are listed here: https://chatgpt.atomiclife.app/, https://www.atomiclife.app/, https://docs.atomiclife.app/

This will be my starting point: https://github.com/rush86999/atomic . A level of integration not possible with Zapier

If you enjoyed this article give Atomic a try that is based on constraint programming to solve your scheduling problems. You can also check out my code on github. It’s open source!

I had to stop using it after loads of conflict files piled up over the years in my notes folder.

I'm trying to switch to WebDAV. Considering Caddy+WebDAV[0] or Peergos[1] or SeaweedFS[2].

[0] https://whhone.com/posts/webdav-syncthing/

[1] https://github.com/search?q=repo%3APeergos%2FPeergos%20webda...

[2] https://github.com/seaweedfs/seaweedfs/blob/master/weed/comm...

> When it gets too out of hand, people will paper it over with a new, simpler abstraction layer, and the process starts again, only with a layer of garbage spaghetti underneath.

I'm pretty happy that there are S3 compatible stores that you can host yourself, that aren't insanely complex.

MinIO: https://min.io/

SeaweedFS: https://github.com/seaweedfs/seaweedfs (this one's particularly nice and is permissively licensed, in contrast to everything else)

There was also Zenko, but I don't think they gained a lot of traction for the most part: https://www.zenko.io/

Of course, many will prefer hosted/managed solutions and that's perfectly fine, but at least when you run software yourself, you are more in control over it and for the most part can also make the judgement on how hard it is to operate and keep operational (e.g. similar to what you'd experience when running PostgreSQL/MariaDB/MySQL or trying to run Oracle).

Whoops: WebDAV:

https://news.ycombinator.com/item?id=39417503

SeaweedFS supports WebDAV. https://github.com/seaweedfs/seaweedfs/wiki/WebDAV

I'm not able to find if both/restic supports mounting backups as WebDAV, but in theory there's nothing stopping you.

It's 100% user space (expose a rest service) and supported by a bunch of file-browsers with a bit of a network aware component to it as well.

If you want/need to take out the metadata, there's some nice solutions for that https://github.com/seaweedfs/seaweedfs

I posted this on https://github.com/seaweedfs/seaweedfs/discussions/5290

I like the idea of using SeaweedFS as an intermediate layer with object write notifications going to SQS, RabbitMQ, or a local file, which could also allow me to observe the changes to different files through a metric collection layer like Prometheus and Grafana.

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet.

Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing

I've actually been looking for more open alternatives, but haven't found much.

Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively: https://github.com/scality/cloudserver/issues/4986 (their Docker images on DockerHub were last updated 10 months ago, which is what the homepage links to; blog doesn't seem active since 2019, forums don't have much going on, despite some action on GitHub still)

There was also Garage, but that one is also AGPL v3: https://garagehq.deuxfleurs.fr/

The closest I got was discovering that SeaweedFS has an S3 compatible mode: https://github.com/seaweedfs/seaweedfs