Paperless-ngx: scan, index and archive all your physical documents(github.com)
github.com
Paperless-ngx: scan, index and archive all your physical documents
https://github.com/paperless-ngx/paperless-ngx
28 comments
Paperless-ngx is fantastic! I’ve been running it for a while and it works great!
I wrote an iOS [1] app to connect to you instance and it’s open source [2].
[1] https://apps.apple.com/de/app/swift-paperless/id6448698521
[2] https://github.com/paulgessinger/swift-paperless
I wrote an iOS [1] app to connect to you instance and it’s open source [2].
[1] https://apps.apple.com/de/app/swift-paperless/id6448698521
[2] https://github.com/paulgessinger/swift-paperless
[deleted]
After scanning a document, how is it different than any other document I have as a file (other than it being not-very-editable)? i.e. is this a general-purpose document management system, or - what?
> The easiest way to deploy paperless is docker compose
Ok, that's a first red flag.
> The easiest way to deploy paperless is docker compose
Ok, that's a first red flag.
Go ahead man, manually install and configure redis, mariadb, gotenberg, and tika to see if you like the software. It's a free country.
Not a general purpose one really, but it is a document management system. It's aimed at incoming mail. You get automatic OCR and learned classification / tagging / date finding.
And "docker compose up" is the easiest way to deploy things these days in general. That's got nothing to do with this software specifically.
And "docker compose up" is the easiest way to deploy things these days in general. That's got nothing to do with this software specifically.
> After scanning a document, how is it different than any other document I have as a file (other than it being not-very-editable)?
You don't want to use paperless-ngx for editable stuff really. You want to use it for stuff like bills, invoices, and business records.
Once it's in paperless, it's searchable and you don't have to worry about where it is. As long as the scan is good it will grab the OCR and then you can search for things like account number. My uncle basically scans everything bill related into his instance and then shreds the paper.
You can also tag documents and search by tag. Also since it's a web app if you can do the self-hosted thing it works well on the phone.
You don't want to use paperless-ngx for editable stuff really. You want to use it for stuff like bills, invoices, and business records.
Once it's in paperless, it's searchable and you don't have to worry about where it is. As long as the scan is good it will grab the OCR and then you can search for things like account number. My uncle basically scans everything bill related into his instance and then shreds the paper.
You can also tag documents and search by tag. Also since it's a web app if you can do the self-hosted thing it works well on the phone.
I have my printer set to scan and save the files to a NFS. Paperless-NGX picks it from there, does OCR and saves it. I guess I could just leave it on the NFS, but I do like the UI of P-NGX.
I have dedicated scanners at my 2 business locations with shortcuts to SFTP scans onto the server. paperless-ngx monitors the folder and automatically ingests the document. literally just two button presses and any document is digitized, tagged, OCRd, and archived within about a minute. I have the scanners set the file name based on their location so I can tell at a glance where something came from in the paperless inbox view.
Any suggestion for a scanner for this purpose?
https://www.brother-usa.com/products/ads1700w
set up was straightforward and the functionality is great
set up was straightforward and the functionality is great
Take a look at full-duplex multifunctional printers, many times they are cheaper than standalone scanners. Just as an example, a black and white laser like the Brother MFC-L2820DW should last you a long time.
Well, at least it'd be "good enough" to get your feet wet, so to speak - and also give you the ability to test if you're going to stick to it.
I got a Brother ADS-4300N to use with p-ngx, works very well and also is way faster than the usual document scanners on MF printers (duplex is done in one pass, for example)...
I got a Brother ADS-4300N to use with p-ngx, works very well and also is way faster than the usual document scanners on MF printers (duplex is done in one pass, for example)...
paperless-ngx is successor of paperless and paperless-ng. Around that time I moved to https://teedy.io which is also opensource https://github.com/sismics/docs and also support ldap.
I've been itching to give paperless-ngx a shot because I just love it but ldap hasn't yet ended up in the docs but the pull request was merged https://github.com/paperless-ngx/paperless-ngx/pull/5190.
Regardless, I just love how this project just keeps coming back to life
I've been itching to give paperless-ngx a shot because I just love it but ldap hasn't yet ended up in the docs but the pull request was merged https://github.com/paperless-ngx/paperless-ngx/pull/5190.
Regardless, I just love how this project just keeps coming back to life
As someone who is adding SSO to B2C apps, are you an LDAP or nothing kind of person or would you consider things with OIDC/OAuth integration too?
LDAP is such a pain in the ass to integrate with, and it seems like most things are going OIDC these days.
LDAP is such a pain in the ass to integrate with, and it seems like most things are going OIDC these days.
OIDC is not really a replacement for LDAP. SAML2 could be, but OIDC in itself has no concept like group membership.
Kerberos, yes, but LDAP no.
What are your pain points integrating with LDAP? It is pretty simple.
Kerberos, yes, but LDAP no.
What are your pain points integrating with LDAP? It is pretty simple.
OIDC _can_ have group memberships if the provider/client support it via claims.
LDAP is a pain because you have to expose/support a lot of knobs for integration (bind vs anonymous, secure vs unsecure, group format, root DNs, etc.). OIDC is (in theory) a lot simpler for the most part as the bare minimum is discovery URL, client ID, and client secret.
LDAP is a pain because you have to expose/support a lot of knobs for integration (bind vs anonymous, secure vs unsecure, group format, root DNs, etc.). OIDC is (in theory) a lot simpler for the most part as the bare minimum is discovery URL, client ID, and client secret.
And LDAP is a nonstarter for passwordless auth.
Absolutely, would love OIDC/OAuth. I use https://goauthentik.io/. Teedy supports only LDAP so that's what I'm using right now.
Nice, thank you. Ive been busy adding OIDC client support to a household management app (https://homechart.app) and I'm now adding support for making it an OIDC provider too. In theory, you'd already have accounts for all of your household members (ideally with TOTP or WebAuthn), so it should be a good identity provider.
I've been avoiding LDAP like the plague. I think MS is moving away from self-hosted AD, and LDAP really loses its luster for most folks when the self hosted options are something like OpenLDAP.
I've been avoiding LDAP like the plague. I think MS is moving away from self-hosted AD, and LDAP really loses its luster for most folks when the self hosted options are something like OpenLDAP.
So, https://goauthentik.io/ actually supports totp with ldap as well. https://docs.goauthentik.io/docs/providers/ldap#binding--bin...
And the parent makes a good point that OIDC/OAuth does not give group membership.
And the parent makes a good point that OIDC/OAuth does not give group membership.
I wish there was some way to combine paperless ngx with Google docs-like things somehow. Being able to combine living documents and scanned versions would be very helpful. I currently just scan things and upload them to Google Drive as a way to centralize everything.
I suppose I could convert "finished" Google docs to PDF and save them in paperless, but it just seems like these systems will always be disconnected in some way.
I suppose I could convert "finished" Google docs to PDF and save them in paperless, but it just seems like these systems will always be disconnected in some way.
From their docs site:
> Documents are saved as PDF/A format which is designed for long term storage…[snip]
Can someone please tell me what attributes make a given file format more suitable for long term storage over another?
> Documents are saved as PDF/A format which is designed for long term storage…[snip]
Can someone please tell me what attributes make a given file format more suitable for long term storage over another?
Everything for the document (fonts, images, etc) are all stored within the document file. It's entirely self-contained.
Among other things, it usually means that the file type has wide interoperability (which makes it more likely you can open it in the far future) and comes in a format resistant to damage, so if bits are changed or removed, you can still recover the rest of the document (usually this means avoiding compressed formats). As to how well-suited PDF/A is for these aspects, I'm not experienced enough to say.
I've even experimenting a generic usage of Zotero, does not work much, ideally these days we need to manage files NOT in a hierarchy but in a graph, automatically managed, annotating files with links in notes, being able to search titles, links, notes all together.
Zim with attachments for non-teaches it's still limited, too tied to the underlying file system, Zotero and Paperless are way too mechanic and Paperless do not allow note, a separate Dokuwiki with links to Paperless stored docs it's simply way too much overhead...
Long story short it's remarkable the automatic OCR (ocrmypdf), auto-classification, metadata automation etc but it's still not "the universal solution" IMO...