w0ndersp00n

Members
  • Content Count

    19
  • Joined

  • Last visited

Reputation Activity

  1. Like
    w0ndersp00n got a reaction from Tido in DMS Document Management System   
    I don't know why it failed. But here are the steps I took to get Paperless running next to Mayan on my dev/test Odroid:
     
    git clone https://github.com/the-paperless-project/paperless.git cd paperless cp docker-compose.yml.example docker-compose.yml cp docker-compose.env.example docker-compose.env docker-compose up -d I edited docker-compose.env to change variables for Timezone and OCR Languages:
     
    TZ=Europe/Amsterdam PAPERLESS_OCR_LANGUAGES=nld deu eng With these steps, Paperless will be build and run on port 8000. This process takes about 15 minutes on my Odroid C2.
     
    Maybe you can try again with these steps.
     
    One thing I did notice already: the consumption of PDF files takes waaaay longer with Paperless then with Mayan. But in my short test this application actually seems worthwile. I'm going to test it further as well.
  2. Like
    w0ndersp00n reacted to Tido in DMS Document Management System   
    @w0ndersp00n   -  I moved this here, not to hijack the Mayan thread
     
     
     
    Building it, sounds a bit similar to here: https://github.com/armbian/autotests  After cloning,  Igor runs an initial part of the script. Once it configured itself (and you have adjusted the configuration file) you run the script again. A similar approach could be done for DMS Paperless I guess.
     
    I agree, Mayan has business like options. Do you want it for business or private use?
    Not sure what exactly you mean by  web-upload, paperless offers:  Currently, there are three options: the consumption directory, IMAP (email), and HTTP POST.
     
  3. Like
    w0ndersp00n got a reaction from Tido in armbian-config mayan edms deployment fails   
    This script doesn't update the system, it only installs docker when the variable is set. But great to know the build also worked for the Rock Pi!
     
     
    Maybe... I could add an additional variable where you can enter the tesseract-ocr languages. But if this script would eventually be called from Softy, the question would never be asked, so a default install is performed.
     
     
    The Mayan containers can be updated independently, but this script was made for easy set-up. So it'll remove all the containers and create them again on every build. The used images for Postgres and Redis stays the same, the container just gets a new id.
     
     
    I think the yellow line is the cache and is available for other applications when they need it. Mine shows almost the same:
     

  4. Like
    w0ndersp00n got a reaction from Tido in armbian-config mayan edms deployment fails   
    No, installing on bare metal wouldn't lower memory usage. Maybe 1 or 2MiB from the Docker overhead, but isn't worth the trouble of installing Mayan. I'd still recommend a container (Docker or podman). Mayan has high system requirements: https://docs.mayan-edms.com/parts/installation.html#minimum-hardware-requirements
     
    Considering this it simply doesn't make sense to install it on lower end ARM devices. It should have at least 1GiB of RAM, but that is the bare minimum. 2GiB is recommended, so a Raspberry Pi 3 would be the bare minimum for running Mayan EDMS. But a Pi 4 or Odroid C2 with 2GB would be a better choice.
  5. Like
    w0ndersp00n got a reaction from Tido in armbian-config mayan edms deployment fails   
    So with a few modifications in the script from Mayan I was able to build the image on my C2. Building on the C2 with Class 10 SD Card takes about 50 minutes, so I assume that a Raspberry Pi 3 might need more than 1 hour.
     
    However there are some issues which I haven't figured out, since I usually don't write or edit shell scripts.
    The default Installation script pulls mayanedms:latest, however during the build a versioned image is created. This means that the variable DOCKER_MAYAN_IMAGE should be updated for every new version. I don't know if there is some automatic way to do this or if the script needs updating after every release. Right now it's not possible to add additional tesseract-ocr languages. They should be added when creating the container, but since that happens in the script the only way to do that is to remove the container after the script finishes and create it again with the right environmental variable. Another small gripe is the memory usage. On my C2 it uses about 900MiB of memory and on my N2 about 1300MiB, so that's quite a lot.
     
    Besides those bullets it pretty much works ok on my Odroid C2 and N2.
     
    https://gist.github.com/w0ndersp00n/86cd913616d64eb90674aedf4b6f6d0d
  6. Like
    w0ndersp00n got a reaction from Tido in armbian-config mayan edms deployment fails   
    Building on the N2 takes about 5 to 10 minutes, so it's not that bad. The resulting image is about 1.2 GB in size.
    I'm not really someone who can write great scripts, but I'll get out my old C2 and try to make a script that builds the image and then starts Docker with it.