osync VS dockerfiles

I tried googling and see this github repo for a shell tool called osync. Not sure if that's what it is or if that's a "red herring". From reading the description of that tool, it sounds like it's syncing files? With what? From what?

I still use it, because that's what I decided to set up after looking around and people raining praise onto it, but I wouldn't ever recommend it. It's a neat project, it does work if you essentially never touch it afterwards, but it's not a useful one as is if you do want to move things around a bit. I'd much rather use anything else, even proprietary solutions, than have to use Syncthing. When I stop lazing about and rebuild my system, I'm probably moving over to osync or something. Better that than Syncthing.

A tool called osync which might be able to do the job, it's like OS-level solution.

I've been considering simply moving over to osync because the little shit can't even handle a few additional files without crapping out. It works fine, when it works, but I almost don't dare touch it lest it crap itself out again. Its a sync program, adding a folder of some twenty pictures should not make it decide to dig an early grave.

https://blog.jessfraz.com/post/docker-containers-on-the-desk... is the one I remember, a bit old but still useful to see how she does it.

Seems super painful and indirected for a nebulous gain to me, but find your joy however you want I guess

Jess does some awesome stuff and this is literally what you asked for. hollywood

mildly relevant https://blog.jessfraz.com/post/docker-containers-on-the-desktop/

Some of my day-to-day software.

After knowing that saved Chrome passwords and cookies in Linux are not protected against malicious dependencies in our development environment or other apps in our system, I decided to run my core apps in Docker containers, where their data is not accessible without sudo, and a personal understanding of where stuff is being saved.

These docker containers are also an improved version of https://github.com/jessfraz/dockerfiles/

Contrary to the project above, docker-workspaces runs Chrome in a sandbox, encrypts keys with the help of an also dockerized gnome-keychain, and works in tandem with pulseaudio, so you can use wired headphones (i still need to add some dependencies for it to work with bluetooth headphones).

Thank you. As someone who uses containers a lot (even to run local programs, shout out to https://blog.jessfraz.com/post/docker-containers-on-the-desk...) this makes some sense to me.

I'm a little way into the Nix Pills document (https://nixos.org/guides/nix-pills/why-you-should-give-it-a-...) which seems to start the explanation from a place where I can understand.