Henrikus

Thank you Squid for adding the low memory mode, highly appreciated! (some paypal money on the way)

main server has 8GB (one small VM and one small docker), RAM never was an issue yet. backup server has 2GB (cannot be updated), but still manages one small docker. I use the swapfile plugin here.

Hello! First of all thank you so much for this great plugin. What would be the best way to suggest small changes to CA? I understand that Unraid needs a minimum of 4G of RAM and does not (yet) offer a swap file without plugins. Now I may not be the only one having older hardware as a backup server with only one small docker container, which runs fine on 2G of RAM. Since one of the last updates, CA will refuse to work, if RAM is below a certain amount. I can handle this for myself by using the swapfile plugin and remove the error message from CA when needed, but what do you think about the following approach: CA refuses to work with less than 4G RAM *NEW*: CA works with more than 2G RAM + at least 2G swap file (but could still display a warning) Have a nice day!

Hi, I just updated my server to > 6.8 and "fell" into the permissions issue with my go file using a "fetch_key" and "delete_key" as described in this thread. I just wanted to summarize what I found to be working now. According this post, all we have to do is add another copy and a chmod. So now the section in my "go file" for the "fetch_key" looks like this: mkdir -p /usr/local/emhttp/webGui/event/starting mkdir -p /usr/local/emhttp/webGui/event/started mkdir -p /usr/local/emhttp/webGui/event/stopped cp -f /boot/custom/bin/fetch_key /tmp cp -f /boot/custom/bin/delete_key /tmp chmod a+x /tmp/fetch_key chmod a+x /tmp/delete_key cp -f /tmp/fetch_key /usr/local/emhttp/webGui/event/starting cp -f /tmp/delete_key /usr/local/emhttp/webGui/event/started cp -f /tmp/fetch_key /usr/local/emhttp/webGui/event/stopped The "fetch_key" and "delete_key" files needed no changes on my setup.