11–20 of 23 posts
ZFS snapshots every 15 minutes
Oh, that's pretty extreme. May I ask what job you do and why you need such fine grained history?
Earlier quoted context omitted.
Oh, that's pretty extreme. May I ask what job you do and why you need such fine grained history?
I feel like individual snapshots are cheap enough that, if you're going to set up automatic snapshotting (+ pruning) anyway , you might as well keep them pretty fine-grained?
I would save a copy of my main excel spreadsheet with the date as the file name. Once a day. Not perfect but it worked.
A while back I started storing my important files on Dropbox. That at least lets you revert to earlier versions - though I'm not sure how granular it is. I'm sure you can do the same thing with many other cloud-based sites. As an added check, at key moments in a project I'll just add (or increment) the number at the end of my filename, so I'm now working in a new file and can "revert" back to the earlier version just…
Yep. I like that approach for simple personal projects (the only kind I do). Sometimes I just append a date -- myHotNewIdea_9jul2022.txt Same idea, though.
Don't use that format — it doesn't sort correctly. You are better off with _20220709 or _2022-07-09.
Saving a file with different names on occasion seems to be the way the rest of the world does it.
My child does a ton of different layers in her art program, each of which is a separate project... that get saved periodically.
Earlier quoted context omitted.
Yep. I like that approach for simple personal projects (the only kind I do). Sometimes I just append a date -- myHotNewIdea_9jul2022.txt Same idea, though.
> _9jul2022 Don't use that format — it doesn't sort correctly. You are better off with _20220709 or _2022-07-09.
They tend to be complex, expensive and centralized software that require an entire IT team to set up and maintain. Sort of similar to ERP software, and in fact, they often get integrated with ERPs.
Smaller orgs tend to use nothing, or an ad hoc system of file/folder structures and spreadsheets, because they can't justify the cost of PLM. I wish there existed a lightweight option. Git doesn't work well with large binaries and it's merge-based workflow doesn't really apply to CAD anyways. PLM software usually use an exclusive check-out model. There is OnShape, a low cost cloud CAD start-up that was bought by Siemens, which has some PLM features I believe.