making apps, making webs.

Redmine and other ruby on rails apps can have issues with large file uploads or file uploads with a slow internet connection. In redmine you may get the dreaded 502 Bad Gateway error showing up in the user interface. Here are the pieces: Apache, unicorn, rails, and redmine. Short version is you need to set the timeout config variable to something higher... like perhaps 120 seconds.  It's not the best solution, but it will let you upload files. Here is a blog post which describes unicorn.rb configuration . There's a setting in the redmine administration section of the tool to increase the maximum file size if you need to do that. You may find apache error log entries like this: [Thu Jan 30 11:11:08 2014] [error] (103)Software caused connection abort: proxy: pass request body failed to 127.0.0.1:7000 (localhost) [Thu Jan 30 11:11:08 2014] [error] proxy: pass request body failed to 127.0.0.1:7000 (localhost) from 1x.1x.1x.1x () Also, you may also need to change y...

Projects that have X in the name are cool. Engines are cool (especially steam powered ones). Spelling engine 'ngin' gains 17.5 l33t points too. All combined, this makes the name nginx super schwet! I've been using nginx for a while now, and have found it quite good so far. Been moving a couple of websites to it, fooling around with it a lot. So far I've been able to use it for everything I've tried. Some of my apache configs are fairly long... so that is saying quite a bit. On my low memory (512MB) server it has saved quite a bit of memory - even though I've only moved over a couple of websites. Along with the cherrypy memory reduction work I did recently, my server has a bit more room to breathe... (and for me to waste memory on hosting other websites! ya!). Nginx has a good reputation as being rock solid - so I hope it holds true for me. Then perhaps I can get rid of apache completely (on this one server). I've tried to replace apache with other...