Checking in the index is a very bad idea. Instead, the index should be
in the shared directory of your deployment, and releases should symlink
to this shared index.
In deploy.rb, this would look like this:
<<-DESC
Create a shared index dir.
All deployed versions will share the same index, as they share the same
database.
When upgrading ferret, this index might have to be rebuilt.
DESC
task :create_index_dir do
run <<-CMD
mkdir -p -m 777 #{shared_path}/index
CMD
end
<<-DESC
Create a symlink from the current release to the shared index.
DESC
task :create_index_symlink do
run <<-CMD
ln -fs #{shared_path}/index/ #{current_release}/index
CMD
end
# Hooks
task :after_setup do
create_index_dir
end
task :after_symlink do
create_index_symlink
end
>
>> for the index not being recreated problem - maybe it's just a permission
>> issue?
>
>I'm not sure about that as the log messages don't seem to indicate it
>and the server user is the same as the user that created the release
>structure. I do have the index checked in to the repository though (as a
>hack) and maybe the attributes on it are wrong (e.g. the dir's not
>executable).
>
>Thanks,
>Michael
>
>--
>Posted via http://www.ruby-forum.com/.
>_______________________________________________
>Ferret-talk mailing list
>[email protected]
>http://rubyforge.org/mailman/listinfo/ferret-talk
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
