Thanks for that tip Steve.  Unfortunately, I didn't deploy it with
capistrano.  But isn't controlling ferret via cap deploy still
manually controlling it?  I mean every time you want to start|stop
ferret you still have to do cap deploy as opposed to ./script/
ferret_server? And would it be possible to re-deploy with capistrano
now that my site is already running?


Lastly, I am still puzzled by what ./script/ferret_server returns.
For example,

Mac:jazinc marike$ ./script/ferret_server -e production start
starting ferret server...
Loaded suite ./script/ferret_server
Started

Finished in 0.00056 seconds.

0 tests, 0 assertions, 0 failures, 0 errors

Sazima mentioned that this is normal output, but the 'Finished in
0.00056 seconds' implies that aaf/ferret quits. Is there specific
output in ferret_index.log that will clue me in as to whether or not
ferret is behaving normally?

Sorry for all the questions but I'm the only admin on this website and
my other rails websites are not nearly this complex.

Thanks again to all for the assistance.  If I can't figure it out,
I'll be looking to hire one of you.

Regards,
Markus

On Nov 10, 11:28 am, "Steven A Bristol" <[EMAIL PROTECTED]>
wrote:
> On Mon, Nov 10, 2008 at 11:24 AM, marike <[EMAIL PROTECTED]> wrote:
>
> >  Putting RAILS_ENV=script/ferret_server -e production start
> > in the config/environment.rb or config/environments/production.rb,
> > Passenger refuses to start.
>
> I think you've discovered that you'll have to start/stop ferret
> independently of your lovd app. you can do this in you cap deploy
> script if you'd like.
>
> cheers,
> steve
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Lovd by Less" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/lovdbyless?hl=en
Who loves ya baby?
-~----------~----~----~----~------~----~------~--~---

Reply via email to