Sign in through GitHub

Please read for an updated status on RailsCasts:

Learn more or hide this

Jaimie van Santen's Profile

GitHub User: jaimie-van-santen

Site: http://jaimievansanten.nl

Comments by Jaimie van Santen

Avatar

Guess I should've looked better :). Thanks!

Avatar

I've tried to set it up so i can deploy to both a staging and production server, but it hasn't worked out yet. Any spproach to go about it? Its basically the same set of tasks, but with a different server location. Something like cap staging:deploy and production:deploy etc.

Awesome cast tho!

Avatar

For some reason I'm getting this while doing a cold deploy, deploy:setup succeeds however, the repo is on the same server. Tried referencing it through the full ssh url or by giving a local absolute url, no avail.

shell
$ cap deploy:cold 
  * executing `deploy:cold'
  * executing `deploy:update'
 ** transaction: start
  * executing `deploy:update_code'
    updating the cached checkout on all servers
    executing locally: "git ls-remote /home/deployer/projects/blog master"
fatal: '/home/deployer/projects/blog' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
*** [deploy:update_code] rolling back
  * executing "rm -rf /home/deployer/apps/blog/releases/20120322194319; true"
    servers: ["192.168.1.49"]
    [192.168.1.49] executing command
    [192.168.1.49] sh -c 'rm -rf /home/deployer/apps/blog/releases/20120322194319; true'
    command finished in 186ms
Command git ls-remote /home/deployer/projects/blog master returned status code pid 9997 exit 128
Avatar

Hey Ryan,

Thanks a lot for the episode. Do you know how to use Compass in Rails 3.1? Since the regular usage is relying on the older public/stylesheets directory i cant figure how to configure it to work with the newer 3.1 and the 960 Compass plugin.

Thanks anyway!