For a while it’s just data in, which it handles really well. But it really started to shine for me when I needed to find some of the documents. OCR and their search works very well for me.
There are also some interesting thoughts in here: https://skerritt.blog/how-i-store-physical-documents/
What’s the error?
Can you run docker-compose logs
Here’s mine: https://cloud.zell-mbc.com/s/Ac5KQTTxcWNYbNs
I tried to add file it to this post but formatting got completely messed up, hence a link.
Before you run docker-compose you need to change the paperless-app volumes to fit your requirements and set up the variables in .env
Let me throw in Paperless NGX, https://github.com/paperless-ngx/paperless-ngx
:-)
But seriously, I was wondering about the requirement to shutdown the VM’s and couldn’t come up with a solid reason? I mean, even if QEMU/KVM/Kernel get replaced during a version upgrade or a more common update, all of these kick in only after the reboot? And how’s me shutting down VMs manually different from the OS shutting down during a reboot?
I know I am speculating and may not have the fill picture, probably a question for the Proxmox team, there may be some corner case where this is indeed important.
By the way, Mexican or US black strat? :-)
I run this one for a few months now: https://github.com/techsneeze/dmarcts-report-parser
You would expose the port to your host which makes the db acessible by anything running on the host, docker or native. Something like
`port
But I would recommend running a dedicated db for each service. At least that’s what I do.
Isn’t the point about containers that you keep things which depend on each other together, eliminating dependencies? A single db would be a unecessary dependency in my view. What if one service requires a new version of MySQL, and another one does not yet support the new version?
I also run all my databases via a bind mount
`volume
and each service in it’s own directory. E.g. /opt/docker/nextcloud
That way I have everything which makes up a service contained in one folder. Easy to backup/restore, easy to move, and not the least, clean.