I am fairly new in the selfhosting business. I host a few services like Jellyfin or AdGuard, but most of my data just sits on plain SMB shares on my NAS.
I am interested in setting up things like Paperless-ngx, Nextcloud maybe Immich as well. One thing I am struggling with is how to organize all this so I don't have the data scattered around multiple places or in the worst-case even duplicated. I like the simplicity of network shares and the fact that I am not relying on a third-party application to keep being maintained. I am currently not sure I am willing to give that up. However, I am also intrigued by the features these services provide. I know Nextcloud has the option to mount external storage, but I don't know which downsides come with that. It gets more complicated with Paperless. As far as I know you typically have a consume directory where you throw in your data and Paperless stores it using its own system in the media directory. This means I either throw in everything or I suddenly have two locations where my documents are stored. If I would mount that media directory in things like Nextcloud I probably wouldn't be able to find anything because of the different structure and naming scheme.
The idea that I had in mind is that I have a single directory structure of my data that can be used on its own and all these tools are just different frontends and provide different views and information of the same data. Maybe this approach is just something from the past and I should move on.
I should add that I am not planning to expose any of these services to the public. All of this is only accessed from inside my house or using a Wireguard VPN.
- How do you guys handle all this?
- How do you avoid data duplication?
- How do you avoid multiple potential file locations? Is a document in my Nextcloud, in my Paperless or just on the network share?
- Do you prepare in some ways in case an application stops being maintained?
- How has this reliance on multiple services impacted other things e.g. your backups?
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.
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:
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
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.