How to monitor select program's folder for changes to revert if something breaks ?

6 months ago by tdTrX to c/datahoarder

Example

sometimes foobar2000 randomly changes some settings and things break, I don't want to create duplicates (to save space) instead I want to track changes in it.
Same for chromium.

I say select because I don't want the imaging solution

clb92 1 point 6 months ago

Could you perhaps solve it by making specific config files read-only?

path: 0 23468835, hotness: undefined, score: 1, children: 0

qaz 1 point 6 months ago

You could use something like Kopia and only include the files you want

path: 0 23469032, hotness: undefined, score: 1, children: 3

tdTrX 1 point 5 months ago

A program makes changes i many places like the profile folder, app data, registry and for linux and macOS it's different story

path: 0 23469032 23555158, hotness: undefined, score: 1, children: 2

qaz 1 point 5 months ago

It seems like you're referring to dotfiles. You can manage these using a git bare repo.

path: 0 23469032 23555158 23558153, hotness: undefined, score: 1, children: 1

tdTrX 1 point 5 months ago

example in windows chromium browser corrupts it self, and I have a image of the disk or I "only track changes for the program", so I can restore it

path: 0 23469032 23555158 23558153 23589314, hotness: undefined, score: 1, children: 0

@lemmy.ml

login for more options

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

go to feed...

@lemmy.ml

login for more options

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

go to feed...