similar to: [PATCH] Apache Documentation Updates

Running into a strange bug using the mongrel upload progress plugin handler, sitting in front of a simple mongrel. The bug appears on an old Xserve (mac OS X 10.3.9 powerpc), but not on my macbook pro, or even a generic 686 linux box. http://pastie.textmate.org/98341 The gist of the pastie above shows that attempts through the browser and curl are actually hitting the filesController, as

Hi BackgrounDRber''s, I''m helping Obie Fernandez write a chapter on Background Processing in his upcoming Pro Rails book, and wanted to see if I could run it past the group. Any input is appreciated. See attached (word doc, owch)! p.s. thanks Ezra skaar, and File.read(CONTRIBUTORS).collect Cheers, -- Charles Brian Quinn self-promotion: www.seebq.com highgroove studios:

Hi mongrel users! I just posted a bad-ass capistrano file that automates *everything* for setting up an apache2+mod_proxy_balancer and mongrel+mongrel_cluster -- including apache2 setups. It''s based off Coda Hale''s guide and all Bradley''s work at fluxura and RailsMachine (thanks Coda and Bradley!). It''s, well, bad-ass, if I must say so myself. My favorite

committing won''t push to production -- you have tested I assume locally? localhost:3000 shows your changes? if so, I can simply go on to the server where it is deployed and issue: svn export (or svn update) and restart the application for changes to actually propagate. svn log shows your commit, that is all well and good: SeeBQ-MacBook:~/rails_apps/atlrug.org cbq$ svn update U

Hi guys, Thanks to several members I''ve updated the apache best practices docs to include several fixes including the bug reported (by Zed and someone else I believe, sorry for the non-attribution) with IE''s \b instead of b rule for deflate. I also added some success stories from Martins, Phillip Hallstrom, and Jens Kraemer -- and the REMOTE_USER pass instructions from Jon

I added some stuff for the new pre-release with prefix for serving multiple rails apps, and did some in general updates/maintenance to the apache page. Please if anyone wants to add anything, or have any suggestions, , or if you''ve got some clever apache rules / tools / configs -- let me know, or feel free to pull it down and patch yourself. And also let me know if I''ve missed

This might not be a mongrel question so much as an IIS question, and if so, my apologies. I''m needing to switch a (ASP.NET) web application that''s running behind a firewall appliance on IIS on port 8443 under SSL to a rails web application -- a mongrel instance (and perhaps later apache or lighttpd with new mod_core_prox in front of mongrel) on a different server. I remember

I know we already mentioned this before on the list but I couldn''t find it in the archives. Is there a way to differentiate the versions for ruby/mswin32 so that I could run a command like: # sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ --include-dependencies --version 1.0 and have it not prompt me like this: Select which gem to install for your platform

I''ve been hunting the web and reading the mailing lists all day but I''m not finding any guidance on this problem. When I try to talk to my mongrel it simply responds with NOT FOUND and nothing else. I can''t find anything on google because this has to be the second most commond phrase in existence. Any help or guidance would be greatly appreciated. Sincerely, Chuck Vose

Apologizes in advance if this sounds rather dense, but I want to make sure I''m understanding everything correctly. We''re in the process of migrating from Apache2.0/FastCGI to Apache2.0+mongrel (why not 2.2? that story is too long and too uninteresting to recount here, but I will tell you that it involves RHEL and only using RHN rpms). The init script that comes with mongrel

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

I thought all you mongrelians might appreciate this: http://xkcd.com/327/ I haven''t laughed out loud at a comic in a while. I realize it''s a working group but I figure many here might get a laugh today out of this one. Steve

I''m building my first Filter and I''m running into an issue with Ferret::Index::IndexReader#term_docs. As I understand it, index_reader.term_docs should return a term-document enumerator for the entire index: index_reader.term_docs => empty set However, I''m getting an empty set. Interestingly enough, the following: index_reader.term_docs_for(:name,

I''ve seen a couple of workarounds on the mailing list related to expiring cached fragments inside of models, but nothing too clean. Anybody have any suggestions for handling this at the model-level? I have an application is updated outside of the Rails controllers, so I can''t use a Sweeper. The 2 methods I''ve seen: a. Use a callback to generate an HTTP post on a

Hi, My department has a SAN and I''m wondering if it is safe to have all of my mongrel''s share log files stored on the SAN. More specifically, we have 4 machines, each running a couple of mongrel processes. Right now each machine has its own set of log files for mongrel. However, I am thinking that it might be better to put the log files on the SAN and let all the mongrels

Hey All, I just wanted to get other peoples take on problems when running merb in production? Just as Rails used to do, the mongrels tend to get heavy/unresponsive over time so need a good kicking by a watcher daemon like god or monit. However, I have had serious problems getting God to restart the process, as the "merb -k <port>" command doesnt appear to work reliably

I have installed backgroundrb. I can start it. I have read everything I can get my hands on, and have read the list for a few months. I have written a worker, and am ready to start. This worker reads a queue, and processes it (sends queued emails). Sends 10, sleeps for a minute, sends 10 until done - very straightforward. My question is, what would be the best way to run this? I have

Hi, Going through the archive, and just keeping a general watch on this list seems to indicate that there are some issues using scheduling with backgroundrb. I need a worker that will perform some actions on an hourly interval. These actions will require access to several of the models in my application. I am currently using backgroundrb to handle processing of files, where I spawn a worker to

Hi mongrelians, I found myself with an unloaded full production server recently which presented an opportunity to run some performance tests against Mongrel and nginx. I thought this list might have some interest in the results of my tinkering! I actually ran two sets of studies, and Wayne Seguin kindly provided a lot of guidance and support in getting them running. Thanks Wayne! Also,

Hi all, I''m trying to create a worker to send a mail to all the users in my db. Right now I''m doing the tests, this is the code in my worker (Masivo is the ActionMailer subclass): def do_work(args) @progress = 0 @logger.info("MAILER: starting job") records = Record.find(:all) total = records.size records.each_with_index do |record, idx|