Tido

This it what usbimager does if I interpret the docs right
 
 

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.

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

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:
 

I know you are our specialist on  Pi-Hole, and I am grateful for that.
However, the OP had very specific questions/requests like I did the same just recently (Spam).  Then every other post is simply spam that doesn't answer the question.
So, he wasn't wasting your time    he just wanted to know how to get his install back to the state it was before and really get rid of everything.
 
To me, fair enough, because even Linux leaves back some traces (not only Windows) - as I had to learn it the hard-way myself.

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.

For me it show's only removable flash drives (on a linux host). Sounds like a #issue to me? There was a (already fixed in 1.0.3) https://gitlab.com/bztsrc/usbimager/-/issues/10 bug in the mac version which listed a internal drive. As you a on windows 10 @Werner it would be very nice if you open a bug report here: https://gitlab.com/bztsrc/usbimager/-/issues an drop your logs with it. Should be thing of a couple of minutes and you could save at least 1 billion of windows users who would like to write a image to the wrong drive and blame others for it 

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

I wasnt also rude, but I copied a part of his first sentence to my answer BUT added a smiley and did put some more in the additional text.
And I did try to help him with some ideas & links - wasnt that nice enough? 

ahh, finally someone. My Tower only hosts Linux.
 
Did you read the short, but interesting  Documentation  maybe this situation is mentioned already. Because in Linux, as I wrote above does this work.
 
 

Yeah it seems to protect only your system drive in Windows.
A general warning before writing would also be nice. Maybe someone add an issue on gitlab?

Windows 10

All,
 
Don´t know if anybody else did it... but I got Bluetooth running by modifying the device tree and adding support for communication between the RTL8723BS and UART1 and loading the needed RTL8723B firmware.
 
Distro: Armbian Buster
Kernel version: 5.4.30-sunxi64 
 
This is how I did it:
 
1) Create a patch (xx.patch) with the next content and place it in  ~/build/userpatches/kernel/sunxi-current/
 
--- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts    2020-04-06 12:37:45.584912094 +0200
+++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts    2020-04-06 12:37:45.584912094 +0200
@@ -498,6 +498,21 @@
     status = "okay";
 };
 
+/* On Wifi/BT connector, with RTS/CTS */
+&uart1 {
+    pinctrl-names = "default";
+    pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>;
+    status = "okay";
+
+    bluetooth {
+        compatible = "realtek,rtl8723bs-bt";
+        device-wake-gpios = <&r_pio 1 1 GPIO_ACTIVE_HIGH>; /* PM1 */
+        host-wake-gpios = <&r_pio 1 2 GPIO_ACTIVE_HIGH>; /* PM2 */
+        reset-gpios = <&r_pio 1 4 GPIO_ACTIVE_LOW>; /* PM4 */
+        post-power-on-delay-ms = <200>;
+    };
+};
+
 &usb2otg {
     dr_mode = "host";
     status = "okay";
 
2) Run sudo ./compile with your favorite  config (Desktop/server/blablabla)
3) Flash the image to an SD card or eMMC module.
4) Start your Pine64 H64 model-B
4) Connect to a network and run the firmware update/upgrades (armbian-config) and install the Bluetooth tools.
5) DO NOT ENABLE SERIAL 1 !!!! in armbian-config
6) Download the next git repo to your board:  https://github.com/lwfinger/rtl8723bs_bt.git
7) Unpack the archive, run make
8) Copy the next firmware files to /lib/firmwares/rtl_bt:
  sudo cp rtlbt_fw_new /lib/firmware/rtl_bt/rtl8723bs_fw.bin sudo cp rtlbt_config /lib/firmware/rtl_bt/rtl8723bs_config.bin 9) Reboot
 
Expected dmesg output:
 
[   45.107273] Bluetooth: HCI UART driver ver 2.3
[   45.107279] Bluetooth: HCI UART protocol H4 registered
[   45.107281] Bluetooth: HCI UART protocol BCSP registered
[   45.107329] Bluetooth: HCI UART protocol LL registered
[   45.107331] Bluetooth: HCI UART protocol ATH3K registered
[   45.107375] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   45.107509] Bluetooth: HCI UART protocol Intel registered
[   45.107592] Bluetooth: HCI UART protocol Broadcom registered
[   45.107614] Bluetooth: HCI UART protocol QCA registered
[   45.107616] Bluetooth: HCI UART protocol AG6XX registered
[   45.107642] Bluetooth: HCI UART protocol Marvell registered

[   45.845446] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
[   45.849521] Bluetooth: hci0: RTL: rom_version status=0 version=1
[   45.849529] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723bs_fw.bin
[   46.055000] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723bs_config.bin
[   46.096579] Bluetooth: hci0: RTL: cfg_sz 55, total sz 23699
 
[   46.929071] Bluetooth: hci0: RTL: fw version 0x373e6962
 
 
'hciconfig list' output:
 
hci0:    Type: Primary  Bus: UART
    BD Address: 48:46:C1:3A:6B:5F  ACL MTU: 820:8  SCO MTU: 255:16
    UP RUNNING PSCAN ISCAN 
    RX bytes:1982677 acl:3028 sco:0 events:491 errors:0
    TX bytes:91688 acl:232 sco:0 commands:225 errors:0
 
File transfer from Pine to Samsung is working... haven't tested anything else..
 
Regards,
 
__Dirk__ 

@Tido no idea what country is yours  but I can suggest ... use google for searching china pcb prototyping. I have recently used easyeda service, or jlcpcb. They manufacture 5 pcs (of each board, hence 3 times 5 pcs) for as little as 2USD plus delivery. Check their site. They can also do some basic assembly (I was not using that option yet, they can have some parts at their stock, anyway you may discuss the SMD soldering only as THT is simpe one)
 
Happens I have 4 set of boards (as I assembled one set only) and I can send those somewhere, to @Igor for example?

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.

Don't forget the 'grey' cost. I do not replace my "old-power-saving-bulbs" because of the grey energy needed.  Same thing as driving an old car until it breaks or buy a new more efficent car.
 

 
PinePhone UBports Community Edition Pre-Orders Now Open
  https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/
 

I installed it and let everything as it is. Two things I don't like:
1a. To start flashing or writing, the button says in german: Ausschreiben (terrible translation),  just 'Schreiben'  would be much better
1b. When it finished it says. Done. Picture (Bild) written successfully instead of 'Abbild'.  I wonder if a human did the translation.
2. It doesn't remember the window size. It is good it starts small, but I have 24" and I like to see the path-to-the-folder I am about to write.
 
It lists the right devices: I attached an USB-Stick and an SDcard and only these two I was able to choose
And finally, it wrote the Kubuntu 20.04  2,3Gb within 1 min and this inlcudes the writing-verification to my understanding   2300/60 = 38MB/s  
Aside from being fast, Zero-Load on the CPU
 
In opposite to Etcher, it is not ejected at the end of the process. Well, if USBImager ensures proper termination of the process it shouldn't harm if the user unplugs it before ejecting it.
 

Bit off topic, that's what the topic is for
So I've been using the NanoPi M4/V2 for over a half year as main desktop and left my pc off most of the times. That today gave me a nice advantage in my electrical bill.
While the price of electricity goes up, I consumed 8.8% less only by using SBC's instead of my pc. And that not for a full year even. I can still improve with LED lights. And keep using my SBCs.

This does give an example why using ARM can be very benificial. I even made a quick video about it. Not really Armbian related. I don't think I need to convince any of you of the advantages of using arm.
But it is a good thing to think about where we can save money/energy in replacing x86 machines with arm boards.

Arm also has disadvantages off course. Less user friendly, do it yourself... I also talk about that. So you don't need to see the video any more actually, bit if you do, please enjoy.
Greetings, NicoD
 

Currently it does not retries. Only once. Will do two retries, otherwise error.

https://www.google.com/search?q=How+to+remove+existing+docker+container 

I ran it now on Odroid N2 and it gets stuck at:
 

I will ofc not proceed with debugging this 3rd party software, but it would be good to notify the author that there is something wrong ...
 
Armbian config script only calls their installer after installing Docker first: https://github.com/armbian/config/blob/master/debian-software#L1780

I installed it and let everything as it is. Two things I don't like:
1a. To start flashing or writing, the button says in german: Ausschreiben (terrible translation),  just 'Schreiben'  would be much better
1b. When it finished it says. Done. Picture (Bild) written successfully instead of 'Abbild'.  I wonder if a human did the translation.
2. It doesn't remember the window size. It is good it starts small, but I have 24" and I like to see the path-to-the-folder I am about to write.
 
It lists the right devices: I attached an USB-Stick and an SDcard and only these two I was able to choose
And finally, it wrote the Kubuntu 20.04  2,3Gb within 1 min and this inlcudes the writing-verification to my understanding   2300/60 = 38MB/s  
Aside from being fast, Zero-Load on the CPU
 
In opposite to Etcher, it is not ejected at the end of the process. Well, if USBImager ensures proper termination of the process it shouldn't harm if the user unplugs it before ejecting it.
 

I learned about Etcher and the writing verification from TK and since I still use: etcher-1.2.1-x86_64.AppImage    based on their release page in the year 2017.  I will now start to use/test USBimager, I read the manual and it sounds just good.
 
I hope you help us testing too?
 

IS ANYBODY OUT THERE ???
I have improved the How To, Igor improved the Tool even more.  Will you please give it a chance and test your Single-Board-Computer (SBC)  - who doesn't like to test and tinker ;).  If you depend on your installation do a backup of your SDcard first   and then, please give it a try:  https://github.com/armbian/autotests
Report back here or on github if bad or good. If good even more, who doesn't like to hear it works well.
 
Thank you