search for: schwuk

..._service-0.1/bin/mongrel_service:52:in `service_init'' from c:/ruby/lib/ruby/gems/1.8/gems/mongrel_service-0.1/bin/mongrel_service:153 from c:/ruby/bin/mongrel_service:18 It''s only the service that has a problem - running the app via mongrel works fine. cheers, -- Dave Murphy (Schwuk) http://schwuk.com

Whilst monitoring my host I noticed that there were three mongrel_rails processes running for a single (non mongrel_clustered) application. Is this normal? Do the processes share the memory top indicates they''re each using? Cheers, -- Dave Murphy (Schwuk) http://schwuk.com

Any news on the Apache Best Practice Deployment instructions? I''m getting ready to set up a production server, and would prefer to use Apache and Mongrel/Cluster. Don''t think I''ll be able to get the latest Apache though. Do I have to proxy through Pound or something to handle multiple mongrel instances? Any pointers? Any help appreciated, Brett

I''m getting the following error. Which apt-get install <some missing package> do I need to run? looks like some build tools. Building native extensions. This could take a while... extconf.rb:1:in `require'': no such file to load -- mkmf (LoadError) from extconf.rb:1 ERROR: While executing gem ... (RuntimeError) ERROR: Failed to build gem native extension.

...;'ve been mulling over an idea for a book covering Ruby on Rails application deployment. Obvious topics include using Mongrel by itself and with Apache/Lighttpd, load balancers, memcached, and Capistrano. What other topics would you like to see covered in such a book? Cheers, -- Dave Murphy (Schwuk) http://schwuk.com

I''ve written a post covering how to turn your Rails app into a system service with Mongrel. you can read it here: http://schwuk.com/articles/2006/06/29/daemonizing-mongrel Cheers, -- Dave Murphy (Schwuk) http://schwuk.com

I would like first to introduce my self to the community. I am Steve Beyer and I am interested in learning Ruby, ROR, and how to set up a production server. I am going to use OSX for my client/developement system but I would like to get some advice on what operating system you would recommend for a production server. I want to use Mongrel to start and then move up the ladder as my

Hi all, I just wanted to let you know that I built some Debian (Sarge) packages to allow an apt-get only installation of Mongrel, Ruby and friends. Also contained is an init script that is capable of managing multiple applications. Support for the Pen load balancer is also included. More info can be found there:

Hey guys, Ok, basically I coded a ruby on rails CMS to manage a bunch of media files. I am finding that a lot of people are "hot linking" to these media files and would like to prevent this to save bandwidth. Usually in the past, it hasn''t been a problem, I would add something like the following to my .htaccess file RewriteEngine on RewriteCond %{HTTP_REFERER} !^$

Hi *, What''s the best way to find out on which port mongrel is running from within Rails? I have a cluster of mongrels behind a balancer (Pen) behind a webserver (Apache). In Rails, request.port return 80 and request.env[''SERVER_PORT''] returns 3000 (the port of Pen) Any ideas? Cheers, Max

Hello all, I''m new to Mongrel and am very impressed with what I see so far. This thing beats FastCGI hands down, and is even simpler to use than SCGI. Great job Zed! Thanks for all the hard work. I am a bit surprised at the memory usage patterns though. I''m not sure if I''m doing something wrong (most likely I am), or if this is a problem with the app I''m

Hi Folks, I''ve been getting reports of people with serious stability problems in Mongrel. These problems go away instantly when they remove ruby-sendfile. If your mongrel starts up saying that you have "sendfile installed" and that it is using it then **you are wrong**. Remove the gem and don''t use it. I''ll be investigating why it doesn''t really

Hello Folks, After all the troubles people have had with Debian I realize that what I''ve done still isn''t enough for smooth sailing. I''m now going to hold back the 0.3.13.4 release in order to put an end to the Debian problem once and for all. I''m currently planning the following changes: 1) Specific documentation for Debian. Debian will become the only