this post was submitted on 25 Jan 2025
505 points (99.2% liked)
Selfhosted
60177 readers
1168 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thank you. Setting it up seems less daunting now. I'm going to try for setting up emails.
The android app is fairly functionally complete, and I only interact with my phone or tablet. In fact, for desktop tasks I have a Linux Mint VM I just console into from my tablet, a sort of sudo laptop.
In anycase, for manual uploading files my phone is probably easier. But, your advice is good for everybody that's not me, sensible people.
Your comment about bindmounts might have solved my biggest problem with Paperless, in that it doesn't write to my 3-2-1 back up folder directly so I end up 3-2-1ing the whole machine. Which is fine, but I keep multiple snap shots of my LXCs so it's multiples of multiples.
/zpool/important/paperless:/use/src/paperless/originalSpecific file paths aside, would [path to zpool]:[path to originals] have paperless saving the originals to my zpool so I would only have 3 copies instead of 3*#of snapshots?
Indeed it would. That's exactly how I have mine setup; with borg backing up the originals folder from the host.
If you are making this change to an existing installation; remember to copy the contents of the current originals folder out of the container and into the host folder you intended to bind mount, before you change the mount.
So, copy the contents of container:'/use/src/paperless/original' place them in host:'/use/src/paperless/original', THEN add your bind mount to the container config.
Otherwise you may lose the contents of the folder within the container and have to retrieve it from a backup.
My server is full of bindmounts. Too many bind mounts. It causes a host of permissions issues if I'm honest. There wasn't a storage problem I didn't solve with bindmounts. Except this one, this one I decided I had to have interact over SMB or some shit.
I remember, I tried to solve it with bind mounts before. I couldn't figure out why it wasn't saving to /mnt/important/paperless/... I think when I get to /originals it's going to look like ./originals/mnt/important/paperless/... Somewhere it's going to look like that. Urgh
Thank you. With that problem solved Paperless is, currently, perfect for my needs.