1) ignore client timeouts (seems that picobrew firmware doesn't wait for a response and is a fire and forget for data logs)
2) disable all error and access logging for /socket.io requests... these are annoying me so much
3) symlink the nginx config for picobrew_pico from the application installation folder (/picobrew_pico/scripts/pi) instead so git pull can update the nginx configuration (this paired with @cgalpin's ideas around running a script post git pull, https://github.com/chiefwigms/picobrew_pico/pull/266, can restart nginx if needed based on file modification date)
1) ignore client timeouts (seems that picobrew firmware doesn't wait for a response and is a fire and forget for data logs) 2) disable all error and access logging for /socket.io requests... these are annoying me so much 3) symlink the nginx config for picobrew_pico from the application installation folder (
/picobrew_pico/scripts/pi
) instead sogit pull
can update the nginx configuration (this paired with @cgalpin's ideas around running a script post git pull, https://github.com/chiefwigms/picobrew_pico/pull/266, can restart nginx if needed based on file modification date)