Jump to content

T0a

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

4 Neutral

About T0a

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, I also own a Fujitsu d3644-b board and found this thread while searching for fan control with unRaid. I bought two NF-A12x25 fans (4 pin pwm) as I wanted to move my unRaid build from the hall to my living room. Unfortunately, the mainboard bios fan control has no silent mode (full, auto and enhanced). Thus, I was trying to control the fans via unRaid - finding it lacking the driver support. There are a lot of people owning this mainboard, because it was highly recommended in c't and this NAS build guide. @limetech Could you please consider adding the driver to unRaid 6.9.0?
  2. I'm sorry, I think this is not possible ATM. However, you can search in the projects issue tracker for this. If you don't find something similar, feel free to open a feature request and describe your use-case. Maybe someone from the community will pick it up and implement it. If you are not aiming to implement this workflow for your business, you might run well with an app for your phone like ScanBot or ScannerPro (Make sure to disable the build-in OCR since it is either bad or runs in the cloud). Otherwise, as already pointed out by @ice pube, the Fujitsu ScanSnap is really popular in business like environments.
  3. This is the only way as far as I know. Is this a problem for you? There is also no multi-user feature. Can you describe your use case for multi-user support? As a workaround you can start multiple Paperless instances - one per user.
  4. Thanks for your reply. I already changed the link in the template. We are waiting for the testing branch getting merged into master. See https://github.com/selfhosters/unRAID-CA-templates/pull/75 👍
  5. You are right. The first container runs `runserver 0.0.0.0:8000 --insecure --noreload` (webserver) and the second one `document_consumer --no-inotify --loop-time 60` (consumer) in „Post Arguments“. Both containers have the /consume folder shared. I will update the install instructions with pictures and making it more precise once I find the time. If you stick to smb shares you might omit the `--no-inotify --loop-time 60` . Thanks for the additional configuration variables. We plan to update the template and I will consider these too.
  6. Glad, I could help! Do you mind asking this question in the new paperless docker template support thread again? I already added a section for scanner. I also created a pull request for changing the support thread in the docker template.
  7. Overview: Support for Docker image paperless in the selfhosters/unRAID-CA-templates repo. Docker Hub: https://hub.docker.com/r/thepaperlessproject/paperless/ Github/ Docs: https://paperless.readthedocs.io/en/latest/ This is the official Paperless Docker support thread. Feel free to ask questions and share information or your experience. I try to update this main post regularly and also incorporate your shares. I also started to contribute features to the Paperless project. You are welcome to help to improve Paperless too as it is a community-driven project. You might also find this old question about Paperless helpful: https://forums.unraid.net/topic/71733-help-with-paperless-dockerhub-unraid/ 1. How to Install Paperless uses a two container setup: (1) a webserver serving your files via the browser and (2) a consumer service that checks for new files in the input directory, doing the parsing and importing the documents to the database. Because unRaid does not support docker-compose, you need to create those two containers from the same template with manual adjustments: 1. Create a "Paperless" share on your array with subfolders for media, consume, and export 2. Install the Paperless webserver 2.1 From the Apps tab, search for "Paperless" 2.2 Configure the Media, Consumption, and Export paths to point at the folders you created in step 1 2.3 Accept the defaults for the remaining variables or adjust as needed. As you get more familiar with Paperless, you may wish to add additional variables that are defined here: https://github.com/the-paperless-project/paperless/blob/master/paperless.conf.example 2.4 Hit Apply to start the container. 3. Create the Paperless superuser 3.1 From the Unraid Docker UI, click the Paperless icon and choose Console. At the prompt, type "./manage.py createsuperuser". Follow the instructions to create the paperless user 4. Install paperless as consumer service to process documents in your /consume folder 4.1 From the Unraid Docker UI, click Add Container and select the paperless template from the [ User templates ] section 4.2 Rename the container to "paperless-consumer" 4.3 Remove the port to avoid port conflicts with the webserver 4.4 Switch to Advanced mode and change the "Post Arguments" parameter to "document_consumer". If you are using NFS, also add "--loop-time 60 --no-inotify" (See FAQ) Now, you should be able to place a document in your /consume folder of your "Paperless" share and recognize it being imported to paperless. 2. Paperless Scan Workflows 2.1 WebDav Scan App with Nextcloud I also want to share my scanning workflow with Paperless and Nextcloud (See https://blog.kilian.io/paperless/ as reference). With the app ScannerPro, I can upload my scanned files to a Nextcloud folder via WebDav from my mobile device. This folder functions as Paperless consume folder and grabs the files and imports them to Paperless. Following steps required for the setup: 1. Mount the paperless /consume folder in the Nextcloud docker container via unRaids Docker template editor 2. Enable the external storage app as Nextcloud admin. The app can be found in the apps dropdown hidden in disabled apps. 3. Add the mounted consume/ folder as local storage for your Nextcloud user with name paperless-consume (Settings -> External Storage) 4. Configure the Nextcloud paperless-consume folder as WebDav target in your scan app 3. FAQ 3.1 Why does the consumer not pick up my files? The consumer service uses `inotify` to detect new documents in the consume folder. This subsystem, however, does not support NFS shares. Thus, you need to start your consumer with "Post Arguments" defined as `document_consumer --no-inotify --loop-time 60`. The document file type might not be supported. Check the consumer logs using the unRaid docker section for warnings and issues. 3.2 How to customize Paperless? All variables from paperless.conf.example can be passed as Docker environment variable to the container. 3.3 What scanner do you use for your paperless home? Paperless user recommendations iPhone with ScannerPro App; one time purchase (@T0a)
  8. I would love to see this as a pull request for the docker template. A few minor remarks from my side: I wouldn't add defaults for Media, Consumption and Export paths, since this may mislead people placing it in their appdata. Though, I like the comment! I suggest to add `PAPERLESS_OCR_LANGUAGE`, defaulted to "eng" with the following description or similar: "Override the language that tesseract will attempt to use when parsing documents. Use a 3-letter language code consistent with ISO 639: https://www.loc.gov/standards/iso639-2/php/code_list.php". Maybe add a short explanation about the unRaid docker template installation i.e. paperless-webserver docker and paperless-consumer docker instances. Maybe add a warning about NFS and inotify issues to the 'Consumption' path such as: "If you are using NFS mounts for the consume directory you also need to change the command to turn off inotify as it doesn’t work with NFS command: ["document_consumer", "--no-inotify"]". Maybe shorter?
  9. @smittyuk Glad I could give something back. The `paperless` image referenced in the official CA template is BTW outdated (also mentioned by @spacecops). The project is now driven by its community (See: https://github.com/the-paperless-project/paperless/issues/470). Use the up-to-date image `thepaperlessproject/paperless` instead. I already proposed the change for the docker template in the UnRaid repository. Change should be on the way. In the meantime you can just stop your container and replace the image and click apply.
  10. With the information from this thread I successfully installed paperless today on my unRaid server. Thanks to @speedyg213 for the wrap-up. Let me briefly summarize the steps to install paperless with the new paperless CA template from 9th Nov 2019. I decided to use NFS mounts also for the consumer folder. So I had to adapt the commands slightly: 1. Create a NFS share with subfolder (e.g. media/ consume/ and data/) 2. Install paperless as web server from CA 2.1. Configure the NFS mounts for media/ consume/ and data/ created in step 1 2.2 Define PAPERLESS_OCR_LANGUAGES (in my case: "eng deu") 3. Login to the paperless container via the unRaid web-interface and issue the following command: "./manage.py createsuperuser". Follow the instructions to create the paperless user 4. Install paperless as consumer service in order to process documents in your /consume folder 4.1 Go to the docker UI, click add container and select the paperless template 4.2 Rename the container to "paperless-consumer" 4.3 Remove the port 4.4 Change the parameter "postargument" to "document_consumer --no-inotify --loop-time 60". This will start the consumer service with a 60 seconds time loop. It also disables the inotify feature, which does not work with consumer/ folders represented as NFS shares. Now you should be also to place a document in your /consume folder of your NFS share and recognize it being imported to paperless. Have a nice weekend everybody! Questions are welcome. ----- Edit ---- I also want to share my scanning workflow with Paperless and Nextcloud with you guys (See https://blog.kilian.io/paperless/ as reference). With the app ScannerPro, I can upload my scanned files to a Nextcloud folder via WebDav. This folder functions as paperless consume folder and grabs the files and imports them to paperless. Following steps required for the setup: 1. Mount the paperless /consume folder in the Nextcloud docker container via unRaids Docker template editor 2. Enable the external storage app as Nextcloud admin. The app can be found in the apps dropdown hidden in disabled apps. 3. Add the mounted consume/ folder as local storage for your Nextcloud user with name paperless-consume (Settings -> External Storage) 4. Configure the Nextcloud paperless-consume folder as WebDav target in your scan app
  11. Hi, check out Home-Assistant (HA). I recently started using it. There is a weather-card and you can configure custom sensors for e.g traffic monitoring (Maybe with Google travel api or Waze api?). Not everything is possible to configure via the Web-Interface. Thus, if you want to have full-control about the lovelance UI, you can enable yaml mode. This site might also be a good source. I also stumbled about this thread a few days ago showing a custom component for UnRaid. However, it is not a public available component.
  12. I have a similar problem. When clicking on the WebUI Button the attached screen appears. By clicking on "agree", I receive the following error after a while: Internal Server Error The server encountered an internal error and was unable to complete your request. The nginx `access.log` contains the following while the `error.log` is empty: 192.168.178.25 - - [17/Nov/2019:19:54:27 +0100] "GET / HTTP/2.0" 500 289 "http://192.168.178.21/Docker" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/2010010 1 Firefox/70.0" 192.168.178.25 - - [17/Nov/2019:19:55:18 +0100] "GET / HTTP/2.0" 500 289 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" 192.168.178.25 - - [17/Nov/2019:19:55:55 +0100] "GET /favicon.ico HTTP/2.0" 500 289 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0 Accessing the WebUI via `http://192.168.178.21:443/` as I did before the upgrade, causes the error "The plain HTTP request was sent to HTTPS port". I am sure that my nginx `default` file contains the latest changes from the commit update nginx site conf due to CVE. Any help?
  13. Does someone own a CPU with UHD 630 graphics unit such as in the i3-8100 and can export the ROM for it? I have the same problem i.e. "cat: rom: Input/output error" exporting the ROM for the GPU as @darianfwith his evga 550ti 1gb. Would be really helpful for me! Thanks.
  14. Thank you. Looks like this mailing list post describes my current problem despite me having also (maybe unrelated) strange hardware errors. I tried the recommendations from this thread getting still the "Input/output error" error. Can somebody provide me a VGA BIOS ROM for Intel core i3-8100 or UHD 630 IDG? I think this is my last option worth trying. $ echo 1 > /sys/devices/pci0000:00/your-i3-integrated-graphics/rom $ cat /sys/devices/pci0000:00/your-i3-integrated-graphics/rom > vbios.dump $ echo 0 > /sys/devices/pci0000:00/your-i3-integrated-graphics/rom I think about buying a ZOTAC GeForce® GT 710 ZONE Edition 2GB DDR3 (or GT730 since ROM is attached here) as a fallback, when I cannot get IDG pass-through with the i3-8100 working. According to @1812 (reference), these cards have native driver support for OSX and should work well with pass-through via UnRaid.