Ok, first up, I’m a Rails newbie. My site is hosted on godaddy.com
Godaddy has the Ferret GEM installed by default. They do not have
acts_as_ferret installed so I can’t use that.
I’m trying to follow the tutorial on the Ferret wiki
http://ferret.davebalmain.com/trac/wiki
It includes all of the code I need, but it doesn’t tell me where to put
any of it. I have several controllers and models and helpers and I have
no idea where I’m supposed to put the code that creates the index.
Can anyone help me out?
Thanks,
Bry
You can copy the acts_as_ferret plugin into the vendor/plugins folder of
your rails app. This will allow you to use acts_as_ferret, it should not
be installed on the server.
Hope that helps.
Ewout
Bryan Deemer wrote:
Godaddy has the Ferret GEM installed by default. They do not have
acts_as_ferret installed so I can’t use that.
I’m trying to follow the tutorial on the Ferret wiki
http://ferret.davebalmain.com/trac/wiki
It includes all of the code I need, but it doesn’t tell me where to put
any of it. I have several controllers and models and helpers and I have
no idea where I’m supposed to put the code that creates the index.
The code at that link is for Ferret, and since you have the gem, you
don’t need it, although I can’t speak for what version Godaddy has
installed and you might need a newer verstion.
acts_as_ferret is a plugin. Plugins install to the vendor/plugins
directory of your rails app, so you can easily use acts_as_ferret.
Here’s a link: http://projects.jkraemer.net/acts_as_ferret/wiki
Thanks for the info everyone. I tried copying the files to the
directory mentioned. Unfortunately when I try to run it, I get the
following error:
uninitialized constant BooleanClause
I did some Google searching and it seems this is due to the fact that
godaddy has ferret .9 installed and not the newer version which seems to
be required for acts_as_ferret.
So I might be back to trying to use ferret all by itself.
Bry
I’m trying to follow the tutorial on the Ferret wiki
http://ferret.davebalmain.com/trac/wiki
It includes all of the code I need, but it doesn’t tell me where to put
any of it. I have several controllers and models and helpers and I have
no idea where I’m supposed to put the code that creates the index.
Hey …
what code exactly? If you’re following the tutorial on
http://ferret.davebalmain.com/api/files/TUTORIAL.html,
then you can place the code almost anywhere in your app 
I would recommend using the acts_as_ferret plugin, as it is much easier
to deal with ferret if you have that
plugin installed. You can copy the code in your vendor/plugin directory,
just like Ewout said…
take a look at the aaf-homepage for further details:
http://projects.jkraemer.net/acts_as_ferret/wiki
there is no need for godaddy to install that plugin, it is sufficient,
if you include it to your rails folder…
Ben
On 22.12.2006, at 13:50, Bryan Deemer wrote:
So I might be back to trying to use ferret all by itself.
Hey …
there’re several versions of the aaf plugin, at least one of them is for
ferret 0.9 …
svn://projects.jkraemer.net/acts_as_ferret/tags/0.2.3/
Ben
Benjamin K. wrote:
Hey …
there’re several versions of the aaf plugin, at least one of them is for
ferret 0.9 …
svn://projects.jkraemer.net/acts_as_ferret/tags/0.2.3/
Ben
Ok, I got this version and tried it and I’m still receiving the
following error:
uninitialized constant BooleanClause
I don’t know what the heck to try now.
Bry
On 22.12.2006, at 16:59, Bryan Deemer wrote:
Ok, I got this version and tried it and I’m still receiving the
following error:
uninitialized constant BooleanClause
I don’t know what the heck to try now.
Bry
If you have a combination of Ferret/AAF working in your development
environment, you can copy the Ferret gem to your vendor folder and it
will be used instead of the one installed by Godaddy. This technique
is known as ‘freezing’ and is often applied to the Rails framework to
make sure everyone in a development team is working with the same
version.
HTH
Andreas
Jens K. wrote:
do you have a more complete stack trace of that error ?
Jens
/usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:123:in
const_missing' #{RAILS_ROOT}/vendor/plugins/acts_as_ferret/lib/acts_as_ferret.rb:176:inacts_as_ferret’
#{RAILS_ROOT}/app/models/tag.rb:3
/usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in
load' /usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:56:inrequire_or_load’
/usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:30:in
depend_on' /usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:85:inrequire_dependency’
/usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:98:in
const_missing' /usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:131:inconst_missing’
/usr/local/lib/ruby/gems-dev/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:133:in
const_missing' #{RAILS_ROOT}/app/controllers/sketches_controller.rb:267:intags’
/usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:941:in
perform_action_without_filters' /usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:368:inperform_action_without_benchmark’
/usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in
perform_action_without_rescue' /usr/local/lib/ruby/1.8/benchmark.rb:293:inmeasure’
/usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in
perform_action_without_rescue' /usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/rescue.rb:82:inperform_action’
/usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in
process_without_filters' /usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:inprocess_without_session_management_support’
/usr/local/lib/ruby/gems-dev/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in
process' /usr/local/lib/ruby/gems-dev/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:indispatch’
/usr/local/lib/ruby/gems-dev/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:150:in
process_request' /usr/local/lib/ruby/gems-dev/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:54:inprocess!’
/usr/local/lib/ruby/gems-dev/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:612:in
each_cgi' /usr/local/lib/ruby/gems-dev/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:609:ineach_cgi’
/usr/local/lib/ruby/gems-dev/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:53:in
process!' /usr/local/lib/ruby/gems-dev/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:23:inprocess!’
/home/content/c/o/m/comicsg/html/gallery_site/public/dispatch.fcgi:25
Andreas K. wrote:
If you have a combination of Ferret/AAF working in your development
environment, you can copy the Ferret gem to your vendor folder and it
will be used instead of the one installed by Godaddy. This technique
is known as ‘freezing’ and is often applied to the Rails framework to
make sure everyone in a development team is working with the same
version.
HTH
Andreas
How exactly do I freeze GEMS? Since I’m using godaddy.com I can’t run
any commands, which is how every tutorial tells me how to do it. So
what files do I put where?
And I don’t have a local development environment, I’m running only on
godaddy.
Thanks,
Bry
On Fri, Dec 22, 2006 at 04:59:54PM +0100, Bryan Deemer wrote:
Ok, I got this version and tried it and I’m still receiving the
following error:
uninitialized constant BooleanClause
do you have a more complete stack trace of that error ?
Jens
–
webit! Gesellschaft für neue Medien mbH www.webit.de
Dipl.-Wirtschaftsingenieur Jens Krämer [email protected]
Schnorrstraße 76 Tel +49 351 46766 0
D-01069 Dresden Fax +49 351 46766 66
You should at least be able to run the rails on your local machine. If
you are using windows, you can do this with InstantRails, on a mac
Locomotive does the job. Once you have rails locally installed, you
should install the ferret gem.
Then, you can test the rails application you are using (and obviously
not developing) on your local machine.
Documentation on freezing is available on <http://nubyonrails.com/
articles/2005/12/22/freeze-other-gems-to-rails-lib-directory>, though I
don’t think the ferret gem can be frozen, since it includes native code.
Can’t you ask the developers of the rails application you are using for
help?
Regards
Ewout wrote:
You should at least be able to run the rails on your local machine. If
you are using windows, you can do this with InstantRails, on a mac
Locomotive does the job. Once you have rails locally installed, you
should install the ferret gem.
Then, you can test the rails application you are using (and obviously
not developing) on your local machine.
Documentation on freezing is available on <http://nubyonrails.com/
articles/2005/12/22/freeze-other-gems-to-rails-lib-directory>, though I
don’t think the ferret gem can be frozen, since it includes native code.
Can’t you ask the developers of the rails application you are using for
help?
Regards
There’s no one to ask since I’m the developer. I’m a one man shop
building my first rails app. I’ll check out the link you sent me and
see if that clears anything up.
Bry