similar to: Explain noob how deploy with 'capistrano' through :git

I am fighting with this for 5 days... i''m getting crazy! Here is my deploy.rb: require "bundler/capistrano" require "rvm/capistrano" # Load RVM''s capistrano plugin. set :rvm_ruby_string, :local # Or whatever env you want it to run in. ''1.9.3'' set :domain, ''www.xxx.com'' set :application,

I am having issues when using unicorn with a Capistrano deployment. >From what I have been able to understand Capistrano uses a scheme in wich every release is deployed inside the releases directory under a unique name and if the transaction was successful, creates a symlink named current that will point to that release. So I end up with a deployment directory such as:

First off thanks very much for all the hard work on unicorn. Alas, we''ve encountered an issue where unicorn fails to spawn new workers that have loaded the incoming revision on a capistrano deploy. I''m not entirely sure the issue is due to unicorn as it appears that bundler was responsible for a similar issue in the past:

I''m NOT working on an enterprisey big time rails application; just something for my personal site. I''ve been deploying via local> git push origin master remote> git pull origin remote> sudo /etc/init.d/httpd restart Trying to decide if this is sufficient, or if learning capistrano and setting that up will give me any advantages over this? Thanks, Dave

Hi, I am reading docs to understand how to deploy with Capistrano my ROR webapps. In guides.rubyonrails.org/2_3_release_notes.html is written: "If you’re one of the (fairly rare) Rails developers who deploys in a fashion that depends on the inspector, reaper, and spawner scripts, you’ll need to know that those scripts are no longer included in core Rails. If you need them, you’ll be able to

I''m doing some searching for deployment options, and I feel like I''m getting buried in a lot of new technology and assumptions that I know all that it''s dependent on. In the past I''ve done small things with PHP where I just dump the app in a folder and everything works out of the box. I found that everyone is using Capistrano, which relies on Subversion

First, I''m trying to do the legwork with utilizing all 4 together because many people say it''s a good combination to use. I already have apache setup (was using it with the PHP version of my site formerly). I''ve installed all gems and dependencies that I need on my slice (using slicehost). I have a fully pushed git repository (master) on github (private git) with one

Is there a way, within capistrano, to deploy not the whole trunk but just stuff tagged a certain way? What I''m trying to accomplish is to let various developers work on different parts of a project, and deploy independantly. Thanks for any help or suggestions. Jim

We''re moving some "internal use" apps to a spare internal machine - instead of a public, shared host. I''m not sure if it''s relevant, but the new machine is running OS 10.3. I''m having a strange problem using Capistrano. It happens on both our development machines, and only when deploying to this server. I run ''cap deploy'' and get:

Greetings, Today I''ve been working out how to begin using Capistrano and so far I''m impressed. Even in my situation, learning Rails and deploying to a single server, it''s incredibly helpful. I do have one small question though: In using Subversion I''ve used the "ignore" feature to ignore my local database.yml file, because my local database and

Hi all, I tried testing with Rspec for first time, following a tutorial. "rspec spec/" works fine but when I try ''autotest'' it gives me the error message below. I also made a gist about it: https://gist.github.com/779265 It seems like a redgreen or ZenTest error. I''m using Ubuntu10, Rails3, Ruby 1.9 and RVM. Any help is appriciated, thanks in advance, gezope

All, Does anyone know if Capistrano/Switchtower actually does anything on the database server as part of the "deploy" task? I''m pretty sure that it doesn''t, but thought I would verify. Thanks, Wes -- Posted via http://www.ruby-forum.com/.

I have two servers up, one will be used for production, one for testing stuff. I''d like to set things up so I can upgrade each one independently. So I could type $ rake deploy That will update the test server. I do that, test it for a few minutes/hours/days whatever, then I can put it onto the main server: $ rake deploy_production Is this possible? If so, how can I do it? Pat

Im trying to deploy with capistrano from win32 to Linux but no success. I''ve been installed: cwRsync to ssh I ran rake remote:exec ACTION=setup --trace and get: Anyone knows how to get capistrano log ssh comunication? Any idea? Thanks rake aborted! End of file reached c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.0.8/lib/net/ssh/transport/version-negot iator.rb:51:in `readline''

I''m wondering if anyone has built a Capistrano task that will deploy mongrel either standalone or along with a rails app. I''ve been looking at possibilities for doing this but still new to using both having switched from using FCGI+Lighty and deploying by hand. Thanks, Curtis

trying like mad to get this to work. cap setup works fine, sets up the dir structure on dreamhost (tho setup doesnt create the "current" symlink). on deploy, i get: * executing "rm -rf /home/USERNAME/dwightnight.org/releases/20060722060159/log /home/USERNAME/dwightnight.org/releases/20060722060159/public/system &&\n ln -nfs /home/USERNAME/dwightnight.org/shared/log

Hello all, i changed today from my local repository to a repository on a server. The repository now lies on the same server where my application is going to be deployed. Everything went fine create my repository on the server and checked out my working copy. After some changes on the code i wanted to deploy my application but it failed. The error is: "svn: Network connection closed

I''ve recently upgraded my box from Ubuntu Breezy to Dapper, and for the life of me can''t figure out why I''m getting this exception thrown. I''ve switched from Switchtower to Capistrano, and when I run rake deploy I get this output: ** [update_code] exception while rolling back: NameError, uninitialized constant Net::SSH::Transport::OSSL

The recent Rails security issue highlighted a concern I''ve had about Rails deploys; namely, you shouldn''t deploy anything to production that you don''t need there. Rails apps have a number of scripts--potential security holes or DOS targets in this case--along with all the other application code you need. There''s no reason you should have script/server, console,

All, I have successfully executed the "deploy" task in Capistrano/Switchtower to establish a symbolic link named "current" which points to the current version of my app. on my remote server. My app. was already deployed to the existing Rails root directory (call it "appname") though. I have Apache fronting my app. through a virtual host whose doc. root is itself