eventually when you get big but probably is
not worth it until you actually know it is a problem.
Cheers-
Ezra Zygmuntowicz
e...@engineyard.com
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
alter the railshandler to not do these lookups
when a config option is set. Merb uses rack middleware to do the
static pages and that can be easily turned off in production. I
believe latest rails does this as well and maybe you can disable these
checks with rack in rails as well?
Che
have it write to wherever you want:
http://mongrel.rubyforge.org/browser/trunk/lib/mongrel/http_request.rb#L47
Cheers-
Ezra Zygmuntowicz
[EMAIL PROTECTED]
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
ng request from Apache (mod_proxy).
I'll try to review the code changes again after I get some sleep (I
really should have been in bed hours ago) and submit a new patch with
any fixes that I make; cosmetic or otherwise.
-- Weave
On Tue, May 6, 2008 at 12:30 AM, Ezra Zygmuntowicz
<[
Hey Brian-
This is pretty kick ass, I'll definitely take a look.
-Ezra
On May 5, 2008, at 8:37 PM, Brian Weaver wrote:
Hello All,
Ticket #30 (http://mongrel.rubyforge.org/ticket/30) has a set of
changes to mongrel that I've written on behalf of
my employer, Raritan Computer, Inc.
org/mailman/listinfo/mongrel-users
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL PROTECTED]
-- EngineYard.com
/mongrel_rails:16"]
>
> Seems to be the same thing that's hanging up the portal app?
>
> Thanks in advance...\
Michael-
What version and patch level of ruby are you running? If you are
using 1.8.6 you need *at least* patch level 110, any patch levels
before that h
upgrade to ruby 1.8.6 p 111. You need at least patch
level 110 or else do not use 1.8.6
Cheers-
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL PROTECTED]
-- EngineYard.com
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
h
/usr/local/bin/merb:16:in `load'
> from /usr/local/bin/merb:16
>
>
> Can anyone offer me any insight into what could be going amiss?
> & sorry again if this is the wrong place.
> Cheers,
> Doug.
> --
> Posted via http://www.ruby-forum.com/.
>
On Jan 23, 2008, at 2:57 PM, Simon Santoro wrote:
> On Wednesday 23 January 2008 23:45:43 Ezra Zygmuntowicz wrote:
>> That's too bad then, you will have to suffer on with apache i guess.
>
> Probably.
>
>> Nginx is a lot more solid then apache is in stability
On Jan 23, 2008, at 2:36 PM, Simon Santoro wrote:
> On Wednesday 23 January 2008 23:03:21 Ezra Zygmuntowicz wrote:
>> Actually the nginx fair balancer has been released for a while. You
>> can read up on it and get it here:
>>
>> http://wiki.codemongers.com/NginxHttp
gineYard built an Nginx plugin that
> does the same (don't think they released it yet).
Actually the nginx fair balancer has been released for a while. You
can read up on it and get it here:
http://wiki.codemongers.com/NginxHttpUpstreamFairModule
Cheers-
- Ezra Zygmuntowicz
--
e
tcp.c: In function ‘tcp_server_address’:
tcp.c:331: error: dereferencing pointer to incomplete type
tcp.c:332: error: dereferencing pointer to incomplete type
tcp.c:335: warning: control reaches end of non-void function
make: *** [tcp.o] Error 1
Thanks
- Ezra Zygmuntowicz
-- Founder & So
articularly troublesome regarding mongrel
> deployment.
Please let's add --clean to mongrel itself. Other then that the only
thing might be to add some additional logic to the gracefull shutdown
of a mongrel server. Say if it tries to
1.8.6 p111 but we do still have a lot of ruby
1.8.5's out there. But I am in favor of making it an optional
dependency.
Cheers-
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL PROTECTED]
-- EngineYard.com
___
Mongrel-users mail
om
>
As far as I can tell this is only exploitable on direct mongrel hits.
I cannot make it happen on mongrels behind nginx or apache.
Cheers-
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL PROTECTED]
-- EngineYard.com
___
tus reports
as well as having a very nice cron like scheduler for jobs. Bj is
more of a work queue that is persistent.
Hope that clears things up, Both of these tools are great for
different circumstances.
Cheers-
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL
roduction environment. For me, a
> crucial capability is X-Sendfile (or something similiar).
>
> Thanks for the help,
> Pete
Nginx works much better then lighttpd for proxying to mongrels. Nginx
has X-Accell-Redirect which is basically same thing as X-Send_fi
proxy balancer
for nginx that works well.
http://brainspl.at/articles/2007/11/09/a-fair-proxy-balancer-for-nginx-and-mongrel
Cheers-
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL PROTECTED]
-- EngineYard.com
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
On Nov 22, 2007, at 4:33 PM, Alexey Verkhovsky wrote:
> On Nov 22, 2007 5:00 PM, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>> but you definitely want to turn [pthreads] off.
>
> Definitely, but... you may need it on, if you use an extension that
> itself relies o
Hi~
On Nov 22, 2007, at 2:47 PM, Benjamin Krause wrote:
> Hey
>
> You need to set the USE flag 'threads' to add pthread support to ruby.
>
> Ben
>
> On 2007-11-22, at 18:53, Zed A. Shaw wrote:
>
>> On Thu, 22 Nov 2007 11:20:37 +0100
>> "Csaba Okrona" <[EMAIL PROTECTED]> wrote:
>>
>>> Hi,
>>>
>>
Yeah I ported evented mongrel to run on packet> it does run and is
faster than threaded mongrel, not quite as fast as event machine
evented mongrel.
The one problem is that the first request after server boot hangs but
then all requests after that are fine. I will continue s
Yeah I have a private ey namespace of devjavu so it would be an
unlimited account.
-Ezra
On Nov 7, 2007, at 7:32 PM, Evan Weaver wrote:
> Ezra, would that be the premium devjavu account? We already have more
> than 5 committers.
>
> Evan
>
> On Nov 7, 2007 10:31 PM, Evan Weaver <[EMA
Evan-
I'd be happy to donate a devjavu account with trac and svn for the
project if you want.
Cheers-
-Ezra
On Nov 7, 2007, at 7:08 PM, Evan Weaver wrote:
> Dear Mongrels,
>
> The same questions keep coming up over and over on the list, which is
> ok, but not really optimal. If we a
The way that I have put this issue to bed for people is with this
crunchy little hack in their environment.rb:
Thread.new { loop { sleep 60*60
ActiveRecord::Base.verify_active_connections! } }.priority = -10
That little baby will keep your database connected.
Cheers-
-Ezra
Hi~
On Sep 7, 2007, at 3:34 PM, Kirk Haines wrote:
> On 9/7/07, Erik Hetzner <[EMAIL PROTECTED]> wrote:
>
>>> And when you are waiting on something like a database, you are doing
>>> it within the DB driver extension, so there are no context switches
>>> happening -- your green threads are blocke
ll eventually have native threads and
may make this situation better but for now such is life.
Cheers-
-- Ezra Zygmuntowicz
-- Founder & Ruby Hacker
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users
ystem is
a database for files already and is much more efficient at storing
files then using the database for it.
Cheers-
-- Ezra Zygmuntowicz
-- Founder & Ruby Hacker
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
On Aug 9, 2007, at 10:37 PM, Alexey Verkhovsky wrote:
> On 8/9/07, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>> So the better way to go about it is to use mongrel_cluster
>> with the
>> --clean and --only options.
>
> Better than runit or telini
the app server. This uses the :use_sudo
variable to determine whether to use sudo or not. By
default, :use_sudo is
set to true.
DESC
task :stop_mongrel_cluster , :roles => :app do
sudo "/usr/bin/monit stop all -g #{monit_group}"
anyone
else is interested. I'm pretty familiar with all the nooks and
crannies in the mongrel source and with it's behavior in the wild ;)
Cheers
-- Ezra Zygmuntowicz
-- Founder & Ruby Hacker
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
ant to run two rails apps on the same domain like
example.com/foo and example.com/bar then you can do it with one
apache vhost but each app will still need it's own set of mongrels to
proxy to.
Cheers-
-- Ezra Zygmuntowicz
-- Founder & Ruby Hacker
-- [EMAIL PROTECTED]
-- Engine Y
erve more then one rails app from the same mongrel
cluster.
Cheers-
-- Ezra Zygmuntowicz
-- Founder & Ruby Hacker
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@
On Jul 13, 2007, at 4:32 PM, Ronald Valente wrote:
> Which web server does mongrel fair best with?
> -Ron
Nginx: http://wiki.codemongers.com/Nginx
Cheers-
-- Ezra Zygmuntowicz
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD
by 1.8.5 and will not run 1.8.6 until
a real release which fixes the thread deadlock bugs is out. So I urge
you to wait until 1.8.6 is actually a production worthy release
before forcing an upgrade on everyone.
Once 1.8.6 is worthy then I fully support this direction.
=>
RUBYAMF::MongrelServlet.new, :num_processors => OPTIONS[:processors])
end
if OPTIONS[:daemon]
daemonize
end
end
config.run.join
You were doing run.join before you daemonized so the daemoinize code
never gets called.
Cheers-
-- Ezra Zygmuntowicz
-
g something new.
>
> --
> Zed A. Shaw
I agree that this all does not belong in Mongrel core. Mongrel core
is already tight as hell. That's what makes it possible to add
features you want by building on top of mongrel. Merb gets really
good perf because it
t;>> to experiment with interfacing with broadcasting clients and audio
>>> players. Anyway, here it is:
>>>
>>> http://pastie.caboo.se/59073
>>>
>>> Thanks,
>>> -carl
>>> --
>>> EPA Rating: 3000 Lines of Code / Gallon (
anyone seen this before?
>
> Cheers,
> Nathan C.
>
>
> --
> Together we can solve any issue.
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
upgrade my ruby version...?
> --
> James.
> http://blog.floehopper.org
James-
Mongrel has *always* required ruby 1.8.4 or later. So you will have
to upgrade ruby if you plan on using mongrel peridion.
Thanks
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-
el on the same port before the other one finishes. This is what
works best for me.
Cheers
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
check process mongrel_<%= @username %>_5000
with pidfile /d
monit.conf that handles
> the cluster?
>
> Many thanks,
> Henry
>
>
> On Apr 3, 2007, at 6:28 PM, Ezra Zygmuntowicz wrote:
>
>>
>> Yes mongrel_cluster handles the pid files. Also it does a better job
>> of stopping mongrels. The problem I had when
x27;ve had this stuff setup.
On Apr 3, 2007, at 4:32 PM, Alexey Verkhovsky wrote:
> On 4/3/07, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>> mongrel_cluster handles the pid files. Also it does a better job
>> of stopping mongrels.
>
> Is there some fundamental reaso
ore
> reliable since you wouldn't have to deal with pid files and
> backgrounding mongrel.
>
> Chris
>
> On 4/3/07, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>>
>> On Apr 3, 2007, at 1:39 PM, snacktime wrote:
>>
>>> Is there anything mon
restarts within 20 cycles then
timeout # something is wrong, call the sys-admin
group mongrel
I wen't for a while using my own scripts to start and stop mongrel
without using mongrel_cluster. But it works more reliably when I use
mong
by/gems/1.8/gems/mongrel-1.0/lib/mongrel/
> configurator.rb:271:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0/lib/mongrel/
> configurator.rb:270:in `each'
> /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0/lib/mongrel/
> configurator.rb:270:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0/bin/mongrel_rails:
> 127:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/mongrel- 1.0/lib/mongrel/
> command.rb:211:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0/bin/mongrel_rails:243
> /usr/local/bin/mongrel_rails:16:in `load'
> /usr/local/bin/mongrel_rails:16
> Mongrel timed out this thread: shutdown
>
>
> --
> -mike
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
On Mar 6, 2007, at 1:23 PM, Rob Sanheim wrote:
> On 3/6/07, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>> snip
>
> Ezra,
>
> What do you use for uptime monitoring? I haven't found anything out
> of the box that can check often enough (ie at least every mi
80% for 3 cycles then
restart# hung process?
if loadavg(5min) greater than 10 for 8 cycles then
restart # bad, bad, bad
if 10 restarts within 10 cycles then
timeout # something is wrong, call the sys-admin
group mongrel
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Ev
nitor
> for a half hour to an hour while the upload churns on with no progress
> :P
Using a flash uploader widget is the best way you can do this
currently. You can have a nice multiple uploads at a time flash
widget that does the progress bar on the client side like it shou
es and use
rails asset_host feature to send static content to a static server.
Or you could ask for rewrite rules to be put in place on the load
balancer to rewrite anything with /images/, /stylesheets/ and /
javascripts/ in the url to be served by the static asset server.
Cheers-
-- E
n with the
least moving parts once he adds this feature.
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
On Jan 22, 2007, at 9:48 PM, Zed A. Shaw wrote:
> Alright folks, after nearly a month of pounding and beating up the
> Mongrel 1.0
> RC1 release we're putting out the official 1.0.1 release.
>
Rock \m/ Thanks for mongrel Zed!
Cheers-
-- Ezra Zygmuntowicz
-- Lead
t may exist.
>request.cleanup if request.interrupted?
>
># And finally, if nobody closed the response off, we
> finalize it.
> unless response.done or client.closed?
> response.finished
>end
>
list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
It's final. I think Zed is waiting to do a mongrel 1.0.1 release in
the next few days to fit with rails strict release versioning
practices ;)
Cheers-
-- Ezra Zygmuntowicz
-- Lead Ra
once it has it. Especially if
you are swamping it so the GC can't keep up.
But 4k and cached I think should be fine. Are you experiencing leaks?
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Ra
Hi~
On Jan 17, 2007, at 11:06 PM, Surendra Singhi wrote:
> Hi,
>
> First of all thanks everyone for their responses.
>
> On 1/18/07, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>
> Some linux distros have weird reporting of processes. I
> have seen it
&
ppening. Are really 9 mongrel processes
>> started
>> instead of three?
>>
>> Please help. Thanks.
>
> --
> Michael Biven
> [EMAIL PROTECTED]
> http://biven.org
> ___
> Mongrel-users mailing list
> Mongrel-users@r
ge} " +
>> "#{options[:source] ? '--source='+options[:source] : nil }
>> " +
>> "#{options[:extra_params] ? options[:extra_params] : nil}"
> 70c69
> < when /\s(\d+).*\(#{platform}\)/
> ---
>> when /\s(\
hink
>>> it has to be a mysql connection timeout but again, the fact that 1
>>> of the 4
>>> always works doesn't lend credence to the timeout theory.
>>>
>>> Has anyone experienced this phenomenon themselves?
>>>
>>> Thanks for any tips/pointers and thanks Zed for all your hard work
>>> with
>>> mongrel.
>>>
>>>
>>>
>>> -Michaelhttp://javathehutt.blogspot.com
>>>
>>>
>>> ___
>>> Mongrel-users mailing list
>>> Mongrel-users@rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>
>>>
>> ___
>> Mongrel-users mailing list
>> Mongrel-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
e
this. In your test cases I also added require 'thread; before the
require 'fastthread' to make them work. How can we verify that this
is a valid fix?
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (
ailing list
>> Mongrel-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
et_host for static content. I don't think you will need this for
the app you are talking about.
I suspect you will end up with 4-6 mongrels per app server and this
will leave you some overhead for what you need to serve. Another
point of reference is the http://yakimaherald.
to run the unit tests and rspec specs. So I
guess this isn't too big of a problem as it will just not use
fastthread during testing. But I would feel better about my tests if
they ran the exact same code as they run in production.
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
0-s00089 ~ # ruby
require 'rubygems'
require 'fastthread'
__END__
ey00-s00089 ~ # ruby -v
ruby 1.8.5 (2006-08-25) [x86_64-linux]
ey00-s00089 ~ # gem -v
0.9.0
It works fine here. But I suspect this will start affecting more and
more folks as they upgrade to rubygems lat
er code file you need to do this:
require 'rubygems'
require 'fastthread'
then require drb and anything else you need.
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
ve the static file
fast. Here is a good blog post about something similar:
http://blog.craz8.com/articles/2006/11/13/lighttpd-proxy-with-x-
sendfile-and-action_cache
CHeers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD
e gem does the mime parsing.
The initialize method here parses the incoming mime stuff including
file uploads or multi part forms:
http://svn.devjavu.com/merb/lib/merb/merb_controller.rb
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Host
quot;, "#{stream} :: #{channel[:host]}"
end
when /\s\d+\./
# Discard other selections from data stream
when /^>/
channel.send_data selections[channel[:host]]
logger.debug line, "#{stream} :: #{channel[:host]}"
else
log
s a complete nginx config for use with mongrel. It does all
the rewites toi assure static content is served by nginx. try this
one out for a more fair comparison
http://brainspl.at/nginx.conf.txt
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, S
ing mongrel_cluster"
start-stop-daemon --stop --retry 15 --oknodo --name
mongrel_rails
eend $? "Failed to stop mongrel_cluster"
}
It's the --retry 15 --oknodo part that does the right thing.
Before I set this we had random mongrel restart failures
think this default could be improved on depending on the
> situation? Think development vs. production deployments.
I am not really sure. I think application/octet-stream is good
default as long as it can be over-ridden then it should meet
everyones needs.
Thanks Zed-
-- Ezra
identifier so that each node writes to its own log files. Doing this
gave us a whopping 25% better performance when compared with all
nodes sharing the same log file.
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (8
ize where I trac issues.
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
g with him
to integrate this so uploads can be parsed once with the fast C mimer
and then just handed off to the next handler with no need to reparse.
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866)
undaries again which is inefficient. Zed is working
on a fast C mime carver and I am going to implement a way to grab the
tmpfile mongrel makes without reparsing it but we haven't made
progress yet.
So let me know if you end up workign on this or if you want to work
with
att Pelletier
> http://www.eastmedia.com -- EastMedia
> http://www.informit.com/title/0321483502 -- The Mongrel Book
> http://identity.eastmedia.com -- OpenID, Identity 2.0
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforg
e running a ton of Xen
VM's on gentoo and it has been absolutely awesome to work with.
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
___
Mongrel-users mailing l
On Nov 8, 2006, at 7:07 PM, Luis Lavena wrote:
> On 11/8/06, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>>
>
> That's good, checked your code but build on win32 failed miserably.
Yeah at this point I hadn't even considered windows yet. I am not
much
talling the gem will build the optimized_locking c extension
after it builds http11.
Grab it here:
http://brainspl.at/mongrel-c-mutex-0.3.14.gem.zip
If anyone has any leaky apps and they want to try this out then
please measure before and after and let me know the results.
t needs to
go in the request StringIO object that gets passed into my mongrel
handler's #process method. Is there a good way to do this? Or should
I just fire up a server and use net/http to test it?
Thanks-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engin
a Mutex, but have patched around the
> problemlematic Array usage by creating my own copy of the Mutex class
> that uses Array in a way that doesn't suffer from the bug.
>
>
> Kirk Haines
Hey Kirk-
Would you mind sharing your patched mutex.rb file? I woudl
appreciate it.
Thanks
o when I had a need for the file
uploads I started out to just write myself a simple mongrel handler
for doing uploads. But then it became fun and I continued on. Now its
really starting to shape up. I love camping but I wanted things my
own way so I built it.
Cheers-
-- Ezra Zygmuntowi
you are most welcome. On the other hand, if Merb
kills your children I am not responsible ;)
Thanks for playing!
Cheers-
-- Ezra Zygmuntowicz
-- Lead Rails Evangelist
-- [EMAIL PROTECTED]
-- Engine Yard, Serious Rails Hosting
-- (866) 5
On Oct 4, 2006, at 8:14 AM, JDL wrote:
> On 10/3/06, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>> Hey Joe-
>>
>> On Oct 3, 2006, at 6:29 PM, Joe Ruby wrote:
>>
>>> Hey Ezra,
>>>
>>> What other gains do you get with virtuali
Hey Joe-
On Oct 3, 2006, at 6:29 PM, Joe Ruby wrote:
> Hey Ezra,
>
> What other gains do you get with virtualizing?
>
> Also, would Xen/virtualizing make these easier?
> - restoring root compromised servers
Yup, you can take snapshots of a VM and restore back to that point in
time without a fu
On Oct 2, 2006, at 4:40 AM, Thibaut Barrère wrote:
> Hi!
>
> I've been using parallels, vmware player, or virtual pc (did not
> try xen yet) for development, testing and experimenting with new
> platforms (and I must say I love them - copy paste a few files, and
> I have a clean deployment
Folks-
James Cox, Alexy Kovyrin and I all huddled up and got nginx working
perfectly with mongrel cluster and rails page caching. So all static
and cached files are served fast by nginx and anything not static
gets sent to mongrel.
http://brainspl.at/articles/2006/09/12/new-nginx-co
On Sep 1, 2006, at 8:58 AM, Ezra Zygmuntowicz wrote:
> HI~
>
> On Sep 1, 2006, at 7:07 AM, Kirk Haines wrote:
>
>> On 9/1/06, Tim Perrett <[EMAIL PROTECTED]> wrote:
>>
>>> If im needing to boost performance how might one go about doing it?
>>
>
HI~
On Sep 1, 2006, at 7:07 AM, Kirk Haines wrote:
> On 9/1/06, Tim Perrett <[EMAIL PROTECTED]> wrote:
>
>> If im needing to boost performance how might one go about doing it?
>
> 35-38/second can move a lot of traffic, as has been mentioned, so long
> as it's 35-38/second for your dynamic traffi
On Aug 31, 2006, at 11:10 AM, philippe lachaise wrote:
> If an in-depth book is due in the forseeable future, what about a
> cookbook then ?
>
> I would kill for a "Rails Deployment and Scaling Receipes" That
> would enable me to start from scratch from a bare hosted Linux Box
> and be up a
On Aug 31, 2006, at 11:12 AM, James Ludlow wrote:
> On 8/31/06, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>>
>> Yeah guys my book will be out in beta around the end of
>> this month.
>> It covers mongrel in depth and also covers pretty much any v
On Aug 31, 2006, at 7:57 AM, James Ludlow wrote:
> On 8/31/06, Dave Murphy <[EMAIL PROTECTED]> wrote:
>> I'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, mem
On Aug 25, 2006, at 12:40 PM, linux user wrote: On 8/25/06, Luis Lavena <[EMAIL PROTECTED]> wrote: On 8/25/06, linux user <[EMAIL PROTECTED]> wrote:[snip] >> No by logging I mean capturing all output on console whether generated by> puts,p,print or by mongrel in a log file.Ohhh, you're trying to de
On Aug 25, 2006, at 9:22 AM, Kirk Haines wrote:
> On 8/25/06, Jarkko Laine <[EMAIL PROTECTED]> wrote:
>
>> No offense, Jean-Eric, but you already asked this two weeks ago [1]
>> and got 7 responses, including one from Zed himself [2].
>>
>> The answer: You can't do that as long as Rails is not th
>
>
> The problem that I am facing is that the output from 'puts, p,
> print' on the console are not captured in the mongrel log file (in
> my case production.log) on Win2K SP4.
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http:
On Aug 25, 2006, at 8:26 AM, Francois Beausoleil wrote:Hi all,If you are using Pound / Pen or another load balancer, I believe youshould read this:http://blog.teksol.info/articles/2006/08/25/subversion-metadata-exposure-on-mongrelMy article refers to Dan Benjamin'shttp://hivelogic.com/articles/2006
On Aug 24, 2006, at 3:52 PM, David Vrensk wrote:On 8/24/06, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote: Memcached is indeed another option. Although it sounded like forjust one Singleton object cache that memcached would be overkill andrequire yet another dependency for the app.
On Aug 24, 2006, at 12:38 PM, Marcus Rueckert wrote:
> On 2006-08-24 08:53:46 -0700, Ezra Zygmuntowicz wrote:
>> Well you can use pound to setup sticky sessions or session affinity
>> but I don't reccomend that as its fragile. I would say your best
>> option is
On Aug 24, 2006, at 8:13 AM, Scott R Brittain wrote: In our app we've a number of singleton ruby classes that cache static data in hashes, things like string values, system config params, etc). In a webbrick environment this works ok, but we find in production we have a problem because we have 4 c
On Aug 20, 2006, at 2:50 AM, snacktime wrote:
> Just thought I'd let you know that your http parser worked great for
> creating an http protocol handler for Eventmachine. It wouldn't take
> that much effort to use Eventmachine for Mongrel, might be worth a
> shot just to see how it does. A few
1 - 100 of 110 matches
Mail list logo
