I've gone overboard with vendor everything, and have checked in all my
gems as well as the rubygem tar file. As a result, I have added the
following task:
task :before_finalize_update, :except => { :no_release => true } do
run "cd #{latest_release} ; ruby deploy/deploy.rb"
end
where my deploy/deploy.rb script does a whole LOT of stuff to get my
checked out code ready to run. If you used
task :before_finalize_update, :except => { :no_release => true } do
run "cd #{latest_release} ; ruby deploy/deploy.rb #{stage}"
end
you should have plenty of room to play...
On Feb 12, 3:33 am, "Rafael G." <[EMAIL PROTECTED]> wrote:
> If you commented the others tasks you would create only
> mongrel_cluster.yml file (If you had database.yml - all required files -
> in your repository no problem else the rails app. will fail).
>
> With this tasks only create the files in shared path, remember that I
> used a trigger/callback that creates symbolics links after
> deploy:update_code. All will run ok before create symlinks in config path.
>
> me escribió:
>
> > I commented out databas_yml, mailer_rb, and local_config_rb since I
> > wanted to address just my issue with the mongrel cluster pointing to
> > the right YAML file at startup. Was this wrong to do, especially
> > commenting out database_yml? Does this mean it is unable to find the
> > location for database.yml?
>
> Surely, you will fail because it lacks the configuration files.
>
> Regards
>
> --
> Rafael Garcia Ortega
>
> rgo.vcf
> 1KDownload
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
