@raulo Do you mean a public instance of #paperlessngx that you have an account on (but others may also have accounts)? Or do you mean hosting your own instance of it on something like AWS?
Now that I have paperless-ngx running and my #scanner is working, any suggestions for a #scanning software for #Linux?
I have an ADF duplex scanner and will mainly scan b&w ("lineart"), but sometimes in color, too. Output files should be PDF, OCR is optional. I need to be able to remove empty back side pages.
Is there anything that supports different, auto-detected page dimensions in a single PDF as well as auto-cropping and skew removal?
Anyone running #PaperlessNGX#rootless using #Podman and #PodmanCompose under #Debian12? The volumes I'm mapping to the host always get chowned to 100999:100999, and that's with USERMAP_UID=1000 and USERMAP_GID=1000 in docker-compose.env.
Playing around with PODMAN_USERNS mainly leads to the container not starting at all (in at least one case because it can't install packages).
a) Set USERMAP_UID=0 and USERMAP_GID=0. Paperless will run as root inside of the container, which maps to your user's UID on the host. Some parts of #PaperlessNGX (e.g. Celery) might warn about running as root, but they don't refuse doing it.
b) Set USERMAP_UID=1000 and USERMAP_GID=1000 (or whatever they are on your host), add "user: 0" to each of the services in docker-compose.yml, start with PODMAN_USERNS=keep-id podman-compose up.
I love #ArchiveBox in lieu of bookmarks that go stale.
I love #paperlessngx for making my collection of articles, papers, technical books, etc. more searchable and manageable.
What I'm missing are two things:
a) an easy pipeline from archivebox to paperless. Basically, if there is a linked PDF or I have a readable PDF, I'd rather have "it" as a Document in paperless than as an archived URL.
b) All of this running as a local app instead of some web stuff.
Ich bin übrigens immer noch sehr begeistert von #paperlessngx, das mittlerweile auf einen #Raspi läuft. So „digitalisiere“ ich fröhlich vor mich hin und arbeite in freien Minuten die Ordner durch.
Ich betreibe auf einem #RPi4 eine #Nextcloud mit Hilfe von #Nextcloudpi. Spricht irgendwas dagegen auf der gleichen Hardware zusätzlich noch #paperlessngx via #Docker zu betreiben (außer die möglicherweise überschaubare Performance)? Können sich die beiden Systeme in die Quere kommen, dass man sich beispielsweise durch ein Update der Dockerungebung den #Webserver von Nextcloudpi zerstört? Habe keine Erfahrung mit Docker, daher die naiven Fragen. Backup vorher ist klar :) #selfhosting
#kudos to @yunohost for providing me an easy home server solution that is running flawlessly since a year on a #RaspberryPI and to the #YunoHost forums community: I had two minor issues with #paperlessNgx and @bookstack and I managed to solve them in less than 10 minutes. Also, I had to say that #BookStack looks very well crafted and may save my "work life" soon. These three projects I mentioned above deserve our contribution! 💗
[Help!] Wenn ich mit FreeFileSync via SFTP eine Datei in den consume-Pfad auf dem Raspberry Pi überspiele, so reagiert Paperless-ngx nicht. Benenne ich diese auf dem Raspberry um, so reagiert Paperless sofort. Auch Kopiervorgänge von einem anderen Verzeichnispfad oder über das Web-Frontend funktionieren tadellos.
Nur die SFTP-Übertragung lässt Paperless kalt ... Irgendeine Idee?