Displaying 15 results from an estimated 15 matches for "lautert".
Did you mean:
later
2007 Feb 08
0
mongrel_rails man page
....I * Default: not set
.br
\fB-h, --help\fP Show help message
.br
\fB--version\fP Show mongrel version
.
.SH SEE ALSO
.BR pen (1), mongrel (1)
.
.SH AUTHOR
Mongrel (http://mongrel.rubyforge.org/) was written by Zed Shaw.
This manual page was written for the Debian system by Filipe Lautert <filipe at icewall.org>.
It might be used and redistributed under the same terms as the program itself.
---
Thanks,
filipe lautert
filipe { AT ] icewall.org
GPG 1024D/A6BA423E
Jabber lautert at jabber.ru
2007 Jan 10
30
Anyway to "dynamically" start/stop mongrel based on web traffic?
Hey all -
I''ve got a question that I haven''t seen addressed anywhere and was
wondering if anyone has put any thought into it or not...
Here''s my setup... I have several *small* sites running apache/mongrel.
Each has a single mongrel instance. Most don''t get any traffic (no one
reads my blog :).
And I was thinking, I could host a couple of more
2007 Dec 25
30
Review of Code for 1.9
Hello Guys,
I''m reviewing the code for 1.9, and forgot about this when we first
spoke on this subject.
The current way we stop threads is using Thread#raise to spread
StopServer exception, which will not work as expected in 1.9.
1.9 will treat raised exceptions as #kill, like JRuby does, so the
worker threads will not finish serving the client and _then_ exiting,
but will be
2007 Nov 07
2
find_pid broken in mongrel_cluster 1.0.4
The find_pid method no longer returns a nil by default which causes
some breakage in cases where the pid can''t be found since the local
variable ''pid'' becomes the entire output of the ''ps'' command. Can you
add this return back in so that it behaves the way it did earlier?
thanks,
eric
2007 Nov 19
1
thanks for the mongrel_cluster fix!
Just as I was composing an elaborate email illustrating that capistrano
version detection was broken, I realized that 1.0.5 fixed the problem :)
While we''re on the topic of code changes-- where is the mongrel_cluster
subversion repository? I looked all over the mongrel site, sorry if I''m
missing something obvious.
Thanks,
John
--
John Joseph Bachir
http://lyceum.ibiblio.org
2007 Mar 08
10
bad URI(is not URI?): c:\boot.ini
Please note this message is not related to my previous one from
yesterday, this is on a different server (textdrive server).
I have only one mongrel application running but ''randomly'' it will go
down, the mongrel.log file shows:
ERROR: undefined method ''request_uri'' for #<URI::Generic:0x5383948 URL:*>
ERROR: bad URI(is not URI?): c:\boot.ini
[FATAL]
2007 Dec 15
6
1.1.2
Hi all,
There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want
fixed before they release it.
If it''s ok with people I''d like to fix that, revert (at least for now)
the proxy response change, and tag that as 1.1.2 and release it.
Anything wrong with this plan?
Evan
--
Evan Weaver
Cloudburst, LLC
2008 May 22
2
gem install of mongrel v 1.1.5 broken in jruby
Can''t install the latest mongrel (1.1.5) in JRuby (jruby revisions
ranging from 6600 to 6750[trunk] checked) -- the platform is not
being identified and it''s trying to do native compilation.
I''m not sure it''s actually a problem with Mongrel or JRuby however --
perhaps there isn''t a mongrel-1.1.5-java.gem on rubyforge?
Some investigation below:
$
2007 Dec 18
3
First Shoot, many more to appear: Rails on Ruby 1.9
Guys,
Subject says everything:
http://www.frederico-araujo.com/2007/12/18/my-first-successful-booting-rails-2-0-2-ruby-1-9-attempt
Even ActionView uses Proc.binding (which isn''t correctly supported in
1.9) it appears that lot of folks will try to put their hands in Ruby
1.9 when it comes out, and of course, try to get Rails with Mongrel
running in it.
Zed, Wayne, Evan and ry: maybe we
2007 Nov 23
6
Fresh install on Debian Etch - Mongrel immediately hangs
Hi,
I just did a clean install of
Ruby 1.8.5
Rubygems 0.9.0
and the Mongrel and Mongrel_Cluster gems.
I used only the Debian Etch package manager, nothing compiled myself.
Now, on a testapp when I do a script/server, I get the:
** Ruby version is not up-to-date; loading cgi_multipart_eof_fix
warning. But it''s not serving my app. Ruby is immediately on 100% CPU
load (and 0.7%
2007 Dec 11
54
1.9
Hey so,
People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the
point of 1.9 for library developers to have time to get ready for 2.0?
It''s not like 1.9 is a production release.
Evan
--
Evan Weaver
Cloudburst, LLC
2007 Oct 22
30
TST is right out
Hi Zed,
I checked in a pure-Ruby URI classifier to Mongrel trunk. Ola''s Java
port of the TST had some bug, and I don''t think it''s necessary in the
first place. The Ruby classifier is around 25 lines instead of the
400-odd lines for the C extension and the 200-odd for the Java
extension. It uses a Regexp which is perhaps shady:
@matcher = Regexp.new(routes.map do
2005 Dec 14
14
Install problems: R-o-R on Debian with mod_ruby
Hello,
I have tried to setup Ruby-on-rails on my debian Linux machine and can
not get it to run. Maybe someone can help.
The following was installed already:
- apache2 2.0.54 (and PHP5)
- Postgresql 8.1
Now, having the ''unstable'' branch in my /etc/apt/sources.list I did:
apt-get install libapache2-mod-ruby
and Apache reports a "mod_ruby/1.2.4 Ruby/1.8.4"
2007 Oct 29
9
Problems with mongrel on NetBSD
I seem to have a (recent) problem with mongrel on NetBSD. I''m running
a development release of NetBSD (called NetBSD-current 4.99.34).
When I start mongrel, it listens on the IPv6 wildcard address, but not
on the IPv4 wildcard:
=> Booting Mongrel (use ''script/server webrick'' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with
2007 Dec 08
14
Small updates and release plan
Hello Guys,
I''ll like to suggest a small release fix before we start doing big
changes: platform fixes.
Current we''re setting MSWIN32 (mswin32) as platform for Windows gem,
but we should be using Gem::Platform::CURRENT instead (i386-mswin32 as
current Ruby windows implementation).
Also, the jruby/java platform need to be defined. That change will
ease the compatibility path