Deploy Permissions Issue #93

Activity

1. EvanK commented on Dec 17, 2013

   

   EvanK

   on Dec 17, 2013

   Contributor

   More actions

   So is the problem just when we're running genesis:permissions? Because it looks like we also moved the bower install to after deploy:update_code, instead of just after deploy:update...
2. jimmynotjim commented on Dec 17, 2013

   

   jimmynotjim

   on Dec 17, 2013

   ContributorAuthor

   More actions

   The only problem I've had is on the permissions, but that doesn't mean there isn't another one farther down. Here's the the terminal output when deploying on a new branch (according to the server, not necessarily freshly branched).

    * 2013-12-05 09:00:15 executing `genesis:permissions'
     * executing [#<Capistrano::Command::Tree::ElseBranch:0x007f8229af7190 @condition="else", @command="sudo -p 'sudo password: ' find -L /var/www/domain.com/new-build/current/web -type d -exec chown :www-data {} \\;", @callback=#<Proc:0x007f8228968b18@/Users/jw/.gem/ruby/2.0.0/gems/capistrano-2.15.0/lib/capistrano/configuration/actions/invocation.rb:13>, @options={}, @skip=false>]
       servers: ["staging.domain.com"]
       [staging.domain.com] executing command
    ** [out :: staging.domain.com] find: `/var/www/domain.com/new-build/current/web'
    ** [out :: staging.domain.com] : No such file or directory
        command finished in 214ms
   *** [deploy:update_code] rolling back
     * executing [#<Capistrano::Command::Tree::ElseBranch:0x007f8229b25bd0 @condition="else", @command="rm -rf /var/www/domain.com/new-build/releases/20131205140015; true", @callback=#<Proc:0x007f8228968b18@/Users/jw/.gem/ruby/2.0.0/gems/capistrano-2.15.0/lib/capistrano/configuration/actions/invocation.rb:13>, @options={}, @skip=false>]
       servers: ["staging.domain.com"]
       [staging.domain.com] executing command
       command finished in 260ms
   failed: "/bin/bash -c 'sudo -p '\\''sudo password: '\\'' find -L /var/www/domain.com/new-build/current/web -type d -exec chown :www-data {} \\;'" on staging.domian.com
   

   According to @mcheck what's happening is that it's setting the permissions on the previous release, and without a previous release on a new branch we get the error.
3. ericclemmons commented on Dec 17, 2013

   

   ericclemmons

   on Dec 17, 2013

   Contributor

   More actions

   So the best thing to do will be to revert #82 and modify the bower event only to address #67
4. mcheck commented on Dec 17, 2013

   

   mcheck

   on Dec 17, 2013

   More actions

   Yes, despite the name :finalize_update has not yet created the symlink, so the genesis:permissions will fail.

   Changing it back to :update will return it to working order.
5. ericclemmons

   added this to the v0.2.51 milestone on Jun 12, 2014
6. ericclemmons commented on Jun 16, 2014

   

   ericclemmons

   on Jun 16, 2014

   Contributor

   More actions

   This is reverted in 5b72085.
7. ericclemmons

   closed this as completedon Jun 16, 2014