similar to: Mongrel 0.13.3.4 Debian packages

Hi all, the current acts_as_ferret trunk is now ported to Ferret 0.10. Get it while it''s hot at svn://projects.jkraemer.net/acts_as_ferret/trunk/plugin Nearly everything works, besides this: - all queries are ORed (no way to tell the QueryParser to build AND queries by default) - more_like_this is broken I''m working with Dave to fix these things soon. The last Ferret 0.9.x

Hi all, I just tagged acts_as_ferret 0.2.2 as the current stable version, so get it while it''s hot ;-) new features: - added support for the multiple models/single index approach. - find out the total number of search results by calling total_hits on the array returned by find_by_contents. fixes: - trac tickets #20 (find_by_contents breaks ferret sorting) and #24

Hi, just wanted to officially announce the release of acts_as_Ferret 0.3.0. As you see, I''m trying to catch up with Ferret''s version numbers ;-) svn://projects.jkraemer.net/acts_as_ferret/tags/0.3.0/ or svn://projects.jkraemer.net/acts_as_ferret/tags/stable/ This release is now tagged stable, so in case anybody has used the old stable release via an svn external, please

Hi all, some days ago I wrote that I once had started porting Luke to Ferret with Ruby/Gtk. I just dug out those sources and put them under version control. It''s far from finished and my first Gtk program, but might be a good start anyway. the code is available at svn://projects.jkraemer.net/inspector/trunk/ If anybody wants to contribute, I''ll be glad to grant commit rights.

Hi, I''m working on an aaf bug report that led me to what I think is a bug in Ferret itself. The snippet at http://pastie.caboo.se/12950 shows the problem, the last two lines should imho only return one result, because of :offset => 1 or :limit => 1, but both return all (that is, 2) results (Ferret 0.10.4). Cheers, Jens -- webit! Gesellschaft f?r neue Medien mbH

Hi! RDig is a small tool to build a Ferret index for the contents of a website or intranet. It contains a simple HTTP crawler and some support for extracting textual content from the fetched pages. I built this to implement a site-wide search for a recent project that combined a Rails application with lots of static html files generated by a CMS. Any feedback is very welcome! Rubyforge

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:

Hi, first of all: great work! I''d like to know which Lucene Version Ferret is based on, in other words: will I be able to read/write indexes created with current lucene trunk ? Thanks in advance, Jens -- webit! Gesellschaft f?r neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Kr?mer kraemer at webit.de Schnorrstra?e 76 Telefon +49 351

Hi folks! Just wanted to let you know that I released aaf 0.4.0 on last weekend. Besides the DRb server it also includes a new lazy loading feature that lets you do ferret searches without actually loading any records from the DB. Useful e.g. for live searches: model: class MyModel acts_as_ferret :fields => { :title => { :store => :yes }, :content => {} } end controller:

Hi! Aaf trunk has undergone several major refactorings the last days, with the result that you can now transparently switch your app from local to remote indexing and back :-) If you plan to scale your app to more than one physical machine, or if you have problems with corrupted indexes and the like under high load, you really should give this a try. I wrote some documentation to get you

[from out-of-band communication with steven, just for the record] Hi! On Wed, Apr 11, 2007 at 01:47:49PM +0200, Steven Garcia wrote: > Hey Jens, > [..] > > 1. Is the Search model just an Active Record object or do I need to > set up a database for it as well (if so then with what columns)? No, that search model is just a plain class that backs your search form. If you want to

Hello Mongrels around the world! Been thinking a way to unify the issue I described in the subject. For those who aren''t aware, mongrel (actually, mongrel_rails) only generate the log file if daemonize was used (-d) That means no log file under windows, due his lack of fork/daemonization capabilities. Now, users that need to run mongrel on windows cannot report and fill the empty

Z-Man, DHH recently said: "And [_why''s] latest work on sandbox looks stellar. Making it drop-dead easy to run multiple Rails applications in the same Mongrel process without conflicts. Thumbs up to both him and Matz for getting Sandbox on track for inclusion with the next Ruby release." Does that mean what I think it means - that one or more Mongrel processes may one day be

Calling All Mongrel Minions! I wanna have some fun and would like this as a Christmas present. The site http://www.workingwithrails.com/ has this lame popularity system that''s kind of irking some of the main Ruby contributors. I think it''s kind of funny, but would like to demonstrate what an army of motivated people can do to these kinds of popularity contests. So, as a

I''m having a strange problem accessing a 1.7GB Ferret index from within Mongrel (1.0.1) on Linux. On OSX a Ferret search through Rails takes a fraction of a second. From the command line, bypassing Mongrel, the search takes about the same amount of time. On Fedora Core 4 a Ferret search from the command line takes a fraction of a second, but the same search through Mongrel never

I''m having a strange problem accessing a 1.7GB Ferret index from within Mongrel (1.0.1) on Linux. On OSX a Ferret search through Rails takes a fraction of a second. From the command line, bypassing Mongrel, the search takes about the same amount of time. On Fedora Core 4 a Ferret search from the command line takes a fraction of a second, but the same search through Mongrel never

I''m taking a stab at creating a parser to parse the server response using the mongrel parser as a base. Never having used a parser like Ragel before in my life, I''d like some input on the following for parsing an http server response. This is part of my modified version of http11_parser.rl. In particular what would be better than using ''any'' to match the

Hi all, Tried out the mongrel upload progress plugin with Drb and it works great on my OSX development box, but when putting it into production (Ubuntu Dapper), uploads complete but the app isn''t returning any values for upload progress, and uploads are not showing up in the queue when running upload_client.rb. Before anyone asks, yes, I''m running both the mongrel instances and

I''m using a cluster of mongrels behind an apache 1.3 proxy pass. I''ve been passing the request to pen, which in turn balances the cluster of mongrels. Now, I''d like to be able to use a different server to send the static files created by the rails application, so I tried to replace pen with nginx. Everything seems to work fine except the environment variable REMOTE_ADDR.

Time for some all time pimpage folks. Me and Matt Pelletier wrote a small PDF book on Mongrel entitled: "Mongrel: Serving, Deploying, and Extending Your Ruby Applications" since we really wanted you to know what it was about. It''s published by Addison Wesley Professional, has just over 100 pages of goodness, and is available for $14.99 at: http://safari.oreilly.com/0321483502