Comment on Data organization
5ymm3trY@discuss.tchncs.de 1 day agoAs I have said in the other comment: I already use Docker and docker-compose for all the services I host. They are also all configured to use bind mounts instead of volume mounts, so that I am in control where everything is located. I heard about Proxmox, but I never really looked into it because never saw the need for something different than a docker container. I also don’t have a dedicated server. All my services are running as Docker containers directly on the NAS.
I am not a fan of data duplication, disk space aside. You are pretty much guaranteed to have diverging file structures sooner or later. I don’t want to look up a file on three different applications just to find the newest version of it. I know you can use rsync and a cron job, but that just adds more complexity to a problem that I don’t want to have in the first place. This might work for something like a read-only backup like i presume you do with Paperless and OpenCloud, but I am not sure how this handles a case where, at least in theory, your files can be changed, renamed etc. in multiple different locations.
How do you handle your Paperless documents? Do you have a local file structure that you manage on your own for these documents or do you shove them all into Paperless and process them entirely in there (naming, tagging, etc.)?
I get your idea of trying things out even though it might result in temporary data duplication to find the way that works best for me. I am just curious how other peoples workflow looks like. Maybe I can also learn from the mistakes other people made in the past :)
Scipitie@lemmy.dbzer0.com 1 day ago
Paperless specifically: yes, shoving everything in it.
But I have honestly no idea what kind of data you have that are suitable for paperless AND have different versions.
I just checked mine, for me it’s… Zero. Not a single item, by definition, is in Paperless that can receive an update.
If it’s updatable personally I have everything version controlled - and I mean EVERYTHING, from CV over tutorials to construction ideas - hosted locally on forgejo.
5ymm3trY@discuss.tchncs.de 1 day ago
Good point. My documents share on the NAS just isn’t organized in a way that it only contains documents that are in a final state like PDFs of your electricity bills or something. It might also contain a spreadsheet comparing different options of a thing I want to buy. I don’t want to loose that file hence its on the NAS, but I also don’t need to keep track of it in Paperless especially not if it isn’t finished and can change next week. I also don’t need to have the overhead of a version control system because its not that important either.
That is actually what I am planning to setup as well. I think I could live with an approach like:
Scipitie@lemmy.dbzer0.com 1 day ago
Sounds reasonable. I’d you, like me, need to protect yourself from sabotaging your own system you could even make NAS documents read only to force a manual step in before editing there.
For me the amount of items that should be there are zero following my own concept … But for some (especially shared sheets specifically) I’m too lazy.
Perhaps I should listen to my own advice here zzz
5ymm3trY@discuss.tchncs.de 1 day ago
That is one of the reasons why I want to switch to version control for more important documents. To have a proper file history, depending on the file type look at a diff to check if something was an accidental edit or an uncommitted change and also that I can work locally and have the NAS only as a mirror and backup.