* executing `deploy:check_revision'
fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
WARNING: HEAD is not the same as origin/master
but it's worked fine to call cap deploy:cold every time.
Finally fixed it. I forgot to replace a couple other 'blog' with 's. I wasn't specifically able to push the change out by updating the unicorn.rb file. I ended up renaming the 'unicorn.blog.sock' and that fixed it.
Is there a way to view a log output from Unicorm like WEBrick? My app is deploying correctly, but isn't running correctly off the sever. I'm just getting the useless error pages.
Is there any good way to expose this authentication scheme to http requests? (or JSON)... I'm trying to write exposed apis for an iOS application that needs to talk to a rails app that I used this autentication scheme in.
Can anyone suggest an EC2 image to use?
I get this error as well when I run cap deploy:
* executing `deploy:check_revision' fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree. Use '--' to separate paths from revisions WARNING: HEAD is not the same as origin/master
but it's worked fine to call cap deploy:cold every time.
Finally fixed it. I forgot to replace a couple other 'blog' with 's. I wasn't specifically able to push the change out by updating the unicorn.rb file. I ended up renaming the 'unicorn.blog.sock' and that fixed it.
Is there a way to view a log output from Unicorm like WEBrick? My app is deploying correctly, but isn't running correctly off the sever. I'm just getting the useless error pages.
Is there any good way to expose this authentication scheme to http requests? (or JSON)... I'm trying to write exposed apis for an iOS application that needs to talk to a rails app that I used this autentication scheme in.