0

I'm trying to deploy my application to a 1&1 shared hosting with Capifony.

I'm using the deploy_via: 'copy' strategy.

My deployment fails at the deploy:update_code task.

capifony output:

--> Updating code base with copy strategy
  * getting (via checkout) revision  to /tmp/20140120140204
    executing locally: cp -R . /tmp/20140120140204
    command finished in 242ms
  * Compressing /tmp/20140120140204 to /tmp/20140120140204.tar.gz
    executing locally: tar czf 20140120140204.tar.gz 20140120140204
    command finished in 1428ms
    servers: ["MyApp"]
 ** sftp upload /tmp/20140120140204.tar.gz -> /tmp/20140120140204.tar.gz
    [MyApp] /tmp/20140120140204.tar.gz
    [MyApp] done
  * sftp upload complete
  * executing "cd /kunden/homepages/16/XXX/htdocs/MyApp/releases && tar xzf /tmp/20140120140204.tar.gz && rm /tmp/20140120140204.tar.gz"
    servers: ["MyApp"]
    [MyApp] executing command
 ** [out :: MyApp] tar (child): /tmp/20140120140204.tar.gz: Cannot open: No such file or directory
 ** [out :: MyApp] tar (child): Error is not recoverable: exiting now
 ** [out :: MyApp] tar:
 ** [out :: MyApp] Child returned status 2
 ** [out :: MyApp] 
 ** [out :: MyApp] tar:
 ** [out :: MyApp] Error is not recoverable: exiting now
 ** [out :: MyApp] 
    command finished in 148ms
*** [deploy:update_code] rolling back

question:

How can i solve this?

Nicolai Fröhlich
  • 51,330
  • 11
  • 126
  • 130
user2357533
  • 3
  • 2
  • `sftp upload /tmp/20140120140204.tar.gz -> /tmp/20140120140204.tar.gz` -> `sftp upload complete`. The file ain't being uploaded to `~/tmp` but `/tmp`. You don't have read-permisssions for `/tmp` (only write permissions as it seems) and therefore extraction fails. – Nicolai Fröhlich Jan 21 '14 at 16:28
  • The file is uploaded to `~/tmp`, I see it. And my user have read-permissions for `/tmp` – user2357533 Jan 21 '14 at 18:30

2 Answers2

1

capistrano v2

The problem originates from your missing permisssions for the /tmp dir on your shared hosting.

You can change the temporary upload dir using:

set :copy_remote_dir, deploy_to   # upload to the deploy dir instead of /tmp

Now capistrano/capifony will upload to a location that it can actually read from again.

capistrano v3

copy_remote_dir isn't available in capistrano v3.

The tmp_dir variable that was introduced in capistrano/PR#576.

Nicolai Fröhlich
  • 51,330
  • 11
  • 126
  • 130
0

I think the problem comes from the sftp upload function.

it tries to upload in the path starting from my user directory.

~/kunden/homepages/16/XXX/htdocs/MyApp/

And it tries to extract the archive in the path starting from the server root directory.

/kunden/homepages/16/XXX/htdocs/MyApp/

Without changing the temporary upload, I have to create the directory :

~/tmp

I resolve the problem using the scp function. Just have to add this at the end of deploy.rb file :

module UseScpForDeployment
  def self.included(base)
    base.send(:alias_method, :old_upload, :upload)
    base.send(:alias_method, :upload,     :new_upload)
  end

  def new_upload(from, to)
    old_upload(from, to, :via => :scp)
  end
end

Capistrano::Configuration.send(:include, UseScpForDeployment)
user2357533
  • 3
  • 2