deploy:setup not creating “current” directory

1,532 views
Skip to first unread message

Levi

unread,
Feb 7, 2011, 6:27:46 PM2/7/11
to Capistrano
Capistrano v2.5.19
ruby 1.8.7 - local comp
ruby 1.8.7 REE on rvm on server
using passenger and apache
deploy script -
<script src='http://pastie.org/1538866.js'></script>

im working on a osx computer and using ubuntu 10.10 as my git server
and web server. I have been following pragmatic programers dev with
rails book as a guide.

everything has seemed to work fine until I did “cap deploy:setup” --
there were actually no errors when I did this, however the directory
system it setup did not include the current directory symlink.

Does anyone have any ideas why there is no “current" directory being
created?

I also did “cap deploy:check” and everything was ok.

When i did "cap deploy” my application was deployed to my releases
folder with only one error:
"failed: "sh -c 'bundle install --gemfile” (another issue im sure)
Any insight on this issue would be appreciated too!



Thanks in advance!

Lee Hambley

unread,
Feb 8, 2011, 3:51:08 AM2/8/11
to capis...@googlegroups.com
everything has seemed to work fine until I did “cap deploy:setup” -- 
there were actually no errors when I did this, however the directory 
system it setup did not include the current directory symlink.

Does not deploy the code, only setup the directory structure for you, after that you need to `cap deploy` and then `cap deploy:migrations` - then you should have a `current` release. (The setup task doesn't do anything to put the code out to your server)

- Lee
Reply all
Reply to author
Forward
0 new messages