Hi Giuseppe -
I have a couple of tasks that resets permissions for me:
task :restart, :roles => :app do
run " chmod +x #{deploy_to}/current/lib/daemons/someprocess"
run " chmod +x #{deploy_to}/current/lib/daemons/someprocess.rb"
run " mongrel_rails cluster::restart -C
/var/www/#{application}/current/config/mongrel_cluster.yml"
run " #{deploy_to}/current/lib/daemons/someprocessrestart"
end
task :after_update_code do
run "chown -R apache:apache #{deploy_to}/current/public/somefolder"
end
Not sure if thats the "capify-way"... but seems to work fine.
Dave
http://www.silverrack.com
On Dec 7, 2007 6:50 AM, Giuseppe Bertini <[EMAIL PROTECTED]>
wrote:
>
> Hello,
> when I deploy my application via capistrano (using the default recipe):
>
> $ cap deploy
>
> everything appears to go well until the system complains that
> script/process/reaper cannot be found.
>
> It turns out that the whole of 'current' and all subdirectories and
> files newly created on the production server have attributes set to 664,
> which prevents files from being executed.
>
> I can manually fix that:
> $ sudo chmod -R 775 /home/rails/myapp
> $ /home/rails/myapp/current/script/process/reaper
>
> and the application starts flawlessly.
> I am not sure why this is happening. My development directories are all
> 775, and the same goes for the whole deployment tree on the production
> server. It's just that the files fetched from svn by the capistrano are
> given these permissions.
>
> My limited Linux skills are not helping right now...
>
> Thank you all in advance!
>
> Giuseppe
> --
> Posted via http://www.ruby-forum.com/.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Deploying Rails" 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/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---
