Paperless - indexing and archiving scanned documents

[stantropics]

@Hillside502 The author says it is feature-complete ("I am no longer doing new development on Paperless as it does exactly what I need it to" - https://github.com/the-paperless-project/paperless). However, it should be working.

[A Former User]

I'd appreciate it. Paperless has the potential to replace the Scansnap cloud. I have the matching Fujitsu IX 500 scanner.

[ergabergblerg]

@stantropics I tried installing this on my cloudron server to no avail. I think the repo is out of date. Really looking for a document manager on cloudron...

[girish]

@ergabergblerg can you try the repo in https://forum.cloudron.io/topic/1066/mayan-edms/10

[bubonicfred]

There is a forked version being maintained at
https://github.com/jonaswinkler/paperless-ng

[doodlemania2]

@bubonicfred I am starting to package this fork since I am stuck on Papermerge. Hopefully this one will be a bit more cooperative. Will post link when I get something resembling functional.

[doodlemania2]

@doodlemania2 My initial commit is here: https://git.cloudron.io/doodlemania2/paperless-ng

THIS DOES NOT YET WORK

But - I need to do these things and I think it's done:

1. sed in the environment variables to the config
2. create the start.sh (with #1 above)
3. setup the three services in systemd

I've done all of the above previously, I just am short on time, so, if anyone can give me an assist, would greatly appreciate it! If not, will continue just as quick as I can.

[doodlemania2]

@doodlemania2 latest checkin has the start.sh and systemd files getting checked in. Still iterating as time permits.

[doodlemania2]

@doodlemania2 Latest checking (simple one tonight) - I switched from supervisor to the build in gunicorn runner and was able to create a username/password and log in! Woot

Now, it's throwing errors about attempt to write to a read only database, so I suspect the auth mechanism is doing something in /app/code that I'll need to symlink.
After that is:
Get the supervisors to work (some weird ini file error)
Test the app
Cleanup
Final commit before handing it off for cloudron test dev in case anyone wants to see it in the app store.

[scooke]

@doodlemania2 Bravo!

[doodlemania2]

This app is now up and functional. Please test! I'll submit to the appstore for WIP in a day or so after some more cleanup and testing.

https://git.cloudron.io/doodlemania2/paperless-ng/

Note: inbound mail is enabled, but you have to configure it yourself in paperless config. I haven't tested that yet and from the looks of the repo, there are lots of issues with mail at the moment, so we may ship unstable without inbound mail.

cc: @girish

[doodlemania2]

@doodlemania2 just an fyi - this is working well, but the "consumption" directory isn't polling so still tinkering with that. I am able to upload manually and auto tagging and pdf extraction is working. so, we're about 95% there I think.

[scooke]

@doodlemania2 Keep up the good work!

[absnt_mind]

@doodlemania2 Very excited about your efforts on this! I appreciate you, sir! I'm a vanilla PHP and JS developer for the most part, so node, docker, manifests, build scripts, all of it gets a little sketchy if I'm the one on it. I would love to learn how to package Cloudron apps, though. Maybe I'll have a look at some of the material that's available on that here later.
I have been aching for a good document management system with user permissions for probably the last 12 months or so.

[doodlemania2]

@girish - I'm officially stuck. The app is ready and I think the tests might even work except for the consumption directory.

Described my issue here: https://github.com/jonaswinkler/paperless-ng/issues/438.

Tried moving the supervisors around, nothing.

If I run the consume script from shell, works like a champ. Open to ideas.

[jimcavoli]

@doodlemania2 Is that a periodic job? Even if not, could we just hack around it with a small caveat by using the shell command and scheduler add-on? It'd be a minor thing, I think, for the Cloudron package to run an "every minute" or something consumption

[doodlemania2]

@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]

@doodlemania2 Sure thing! Also, didn't know it was inotify under the hood - that has a fraught history with dockerized runtimes, so this is likely your best option anyway

[doodlemania2]

@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!

[girish]

@doodlemania2 I marked this as WIP now! Great progress.