Paperless - indexing and archiving scanned documents
-
@jimcavoli That's a fabulous idea - I will give that a try - it uses inotify on the FS to monitor for changes (intended to always run), but this could be a fabulous workaround! ON IT!
-
@jimcavoli alrighty - that seems to have worked (running it with cloudron scheduler). now just need someone to help me with tests and it can ship!
-
@doodlemania2 I marked this as WIP now! Great progress.
-
hi all,
I was actually working on this a few weeks ago. I forked @doodlemania2's repo and updated it to the latest version. I also enabled SFTP access I am also working to implement the proxyauth addon to pass though to the django app (still wip) as it does not support LDAP natively.
I don't have access to fork in the cloudron gitlab so I had to copy to my github account. You can find the repo here:
https://github.com/campbellmcgregor/paperless-ng-cloudronthanks
-
@ultraviolet would you send me a PR? I'd be delighted to merge those in!
-
@doodlemania2 sure next time I am at a desk I will send you a PR
-
@ultraviolet said in Paperless - indexing and archiving scanned documents:
I don't have access to fork in the cloudron gitlab so I had to copy to my github account
Whoops, sorry about that. By default, accounts cannot fork since we get too much spam. I assume you are https://git.cloudron.io/admin/users/ultraviolet ? I have increased the project limit already.
-
@doodlemania2 sent you a PR
-
@ultraviolet Merged! That's fantastic - great work!!!
-
@doodlemania2 thanks, I may send you another PR in a day or so hit a few walls with the proxyauth.
-
@ultraviolet @doodlemania2 Per https://github.com/jonaswinkler/paperless-ng/discussions/654, it seems if someone knows some python we can add proper ldap support.
-
@girish oooo shiny! @ultraviolet -- that you?
-
@doodlemania2 great work, thank you for making this available.
I built (very smooth) and installed on my Cloudron.
As a noob to paperless-ng, I am not sure what is needed for "processing".
I uploaded few documents to test and they seem stuck in 'processing' in dashboard view.
A tag and correspondent don't seem to get auto-applied.
Is this functionality working ?
Do I need to do something ? -
@timconsidine Seems last was my noob issue.
The dashboard clears eventually and tags can be retro-applied withroot@<app-instance>:/app/code/src# python3 manage.py document_retagger -T
New Q : I'm looking to add schedule tasks but cannot see in doc a list of task.function. Is there one available?
-
@timconsidine Glad you got it working - I'm note sure how the scheduled tasks stuff works - since it does what i need out of the box, I just ignored those
-
@doodlemania2 no problem, I understand, and likewise I have started using it as it does everything I currently want 'out of the box'.
I just don't like to miss a trick by getting even more value out of it by using 'advanced options'.I have to say : thank you again. It's an awesome app, and solves a problem of coordinating docs between users (in my case purchase invoices needing review and input). Previously I have been using a shared folder in Nextcloud, and although that works, I have had issues when some user's sync to Nextcloud stops, and everyong starts shouting at each other because they are seeing different views of the world.
The only things not there which I can identify which would be nice :
-
"tag tree" view, which I notice Teedy has. Just a UI advantage
-
a way to remove tags w/o manually doing so, based on some conditions
But hey ho, just "nice to have" not essentials.
-
-
@timconsidine outstanding! really glad it works for you
-
@timconsidine Hello! To get this installed, did you download the source, cd into the directory and run
cloudron build
thencloudron install
? I only once ever managed to install a non-official app but I totally forget how I did it!One place I get stuck on conceptually is at https://docs.cloudron.io/custom-apps/tutorial/, where it tells us to build:
# build the app $ docker build -t username/nodejs-app:1.0.0 .
What in the world is "username" supposed to be? Just a bit earlier it tells us to
git clone https://git.cloudron.io/cloudron/tutorial-nodejs-app
, so why wouldn't the build section just usecloudron
as the username? And if it isn'tcloudron
but myself, does this mean it is going to be put in a directory in the directory I'm building in? Anyway, this stuff confuses the heck out of me.