Hi!

On Tue, Nov 20, 2007 at 06:07:00PM +0100, Sheldon Maloff wrote:
> (Sorry if some people see this twice. I originally posted this question
> from ruby-forum.com, but didn't realize that the Ferret forum was a
> mirror and that I actually wasn't a member.)
> 
> Anyway,
> 
> I've read all the documentation I could find, and read most of this
> forum, but I'm a still a little confused on running a ferret DRb server.
> 
> All the examples seem to be from the point of view of running the DRb
> server from within the context of a RoR web site. I'd like to consider
> the following scenario:
> 
> Server 1: front-end web server + mongrel cluster
> Server 2: Ferret DRb server
> Server 3: MySQL database
> 
> My question is related to Server 2? Exactly what is it that I have to
> deploy to that computer to have a Ferret DRb server? I understand that
> on Server 1, ferret_server.yml should have a production entry that
> points to Server 2, and that all the models on Server 1 need :remote =>
> :true. But what lives on server 2? Do I just deploy the models folder,
> the config folder and the scripts folder? Or do I deploy an entire copy
> of the web site code?

The DRb server needs at least access to your model classes, I think
the easiest way is to just deploy a copy of your whole Rails app to
the DRb server.
Of course you won't need your views there, but I'd find it easier to 
just deploy the whole app to a second place with capistrano than 
manually ripping the parts needed for DRb off.

Btw, you don't need :remote => true anymore with the current release of
aaf. Just configure your ferret_server.yml for production environment.

Cheers,
Jens


-- 
Jens Krämer
webit! Gesellschaft für neue Medien mbH
Schnorrstraße 76 | 01069 Dresden
Telefon +49 351 46766-0 | Telefax +49 351 46766-66
[EMAIL PROTECTED] | www.webit.de
 
Amtsgericht Dresden | HRB 15422
GF Sven Haubold, Hagen Malessa
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to