Sorry I failed to mention the command I used. I ran the command cap production deploy:check.
I just ran it again and got the following: $: cap production deploy:check Text will be echoed in the clear. Please install the HighLine or Termioslibraries to suppress echoed text . Password:******* DEBUG Uploading /tmp/git-ssh.sh 0.0% INFO Uploading /tmp/git-ssh.sh 100.0% INFO [d53988aa] Running /usr/bin/env chmod +x /tmp/git-ssh.sh on server. domain.com DEBUG [d53988aa] Command: /usr/bin/env chmod +x /tmp/git-ssh.sh INFO [d53988aa] Finished in 0.268 seconds with exit status 0 (successful). DEBUG [86656372] Running /usr/bin/env git ls-remote http://gitserv.domain.com/dba/my_sync on server.opnet.com DEBUG [86656372] Command: ( GIT_ASKPASS=/bin/echo GIT_SSH=/tmp/git-ssh.sh / usr/bin/env git ls-remote http://gitserv.domain.com/dba/my_sync ) Text will be echoed in the clear. Please install the HighLine or Termioslibraries to suppress echoed text . Password:***** DEBUG [86656372] fatal: http://gitserv.domain.com/dba/my_sync/info/refs?service=git-upload-pack not found: did you run git update-server-info on the server? DEBUG [86656372] Finished in 5.518 seconds with exit status 128 (failed). So this gives me a little bit more data to see whats going on I think. On Monday, December 9, 2013 11:38:08 AM UTC-5, Vell wrote: > > Thanks for the response Lee. > > The server I am attempting to deploy to doesn't have an ssh-key on it that > allows me to authenticate without a password. It is only one server that I > am deploying to in this case (another OS X system). This is why I believe > it prompted me for a password. I figured that if the other users that > attempt to deploy, don’t know the password to the server then I’m fairly > safe. It keeps me from having the task of adding users to the authorized > keys file on that server. However, there aren’t that many users, so if I > have to do it I will. > > Right now here is what I have in my files. Sorry for the entries being > ambiguous. > > deploy.rb > > set :application, 'my_sync' > set :repo_url, 'http://gitserv.domain.com/dba/my_sync' > > > # ask :branch, proc { `git rev-parse --abbrev-ref HEAD`.chomp } > > > set :deploy_to, '/users/administrator/scripts/my_sync' > set :scm, :git > > > # set :format, :pretty > # set :log_level, :debug > # set :pty, true > > > # set :linked_files, %w{config/database.yml} > # set :linked_dirs, %w{bin log tmp/pids tmp/cache tmp/sockets > vendor/bundle public/system} > > > # set :default_env, { path: "/opt/ruby/bin:$PATH" } > set :keep_releases, 3 > > > namespace :deploy do > > > desc 'Restart application' > task :restart do > on roles(:app), in: :sequence, wait: 5 do > # Your restart mechanism here, for example: > # execute :touch, release_path.join('tmp/restart.txt') > end > end > > > after :restart, :clear_cache do > on roles(:web), in: :groups, limit: 3, wait: 10 do > # Here we can do anything such as: > # within release_path do > # execute :rake, 'cache:clear' > # end > end > end > > > after :finishing, 'deploy:cleanup' > > > end > > production.rb > > set :stage, :production > > role :app, %w{[email protected]} > > server 'server.domain.com', user: 'administrator', roles: %w{app} #, > my_property: :my_value > > I figured this was pretty much all I needed. > > On Monday, December 9, 2013 3:59:15 AM UTC-5, Lee Hambley wrote: >> >> Hi Vell, >> >> If you are familiar with Cap2, then the fundamentals of Cap3 didn't >> change. >> >> Regarding your query, you look to be doing something non-standard (why is >> high line prompting for a password?) that's definitely nothing from us, and >> appears to be causing some problems. It would appear that one of your >> servers isn't authenticating problems (I realise that's a little bit >> unclear, but it's clearly failing in `net/ssh.rb:215:in `start'`) >> >> I'd say that you need to make sure your SSH keys are working correctly >> before starting with Capistrano! >> >> Good luck. >> >> On Sunday, 8 December 2013 22:59:43 UTC+1, Vell wrote: >>> >>> I looked at the readme and the >>> http://www.capistranorb.com/documentation/getting-started/preparing-your-application. >>> >>> Its a lot of explaining but nothing that explains what the bare minimum >>> is for deploying a ruby application. For instance, my application doesn't >>> require the :web or :db part of the production application. So while there >>> is "lots of stuff" there, there isn't something like the from beginning >>> page that walks you through each part of the setup step by step to >>> understand what your doing and why your doing it. Well at least not that I >>> have seen. >>> >>> Now I just need to understand why I am getting the following: >>> >>> afrosamurai:sync[capistrano]$ bundle exec cap production deploy >>> Text will be echoed in the clear. Please install the HighLine or >>> Termioslibraries to suppress echoed text >>> . >>> Password:********** >>> DEBUG Uploading /tmp/git-ssh.sh 0.0% >>> INFO Uploading /tmp/git-ssh.sh 100.0% >>> INFO [73e91495] Running /usr/bin/env chmod +x /tmp/git-ssh.sh on >>> enterprise.domain.com >>> DEBUG [73e91495] Command: /usr/bin/env chmod +x /tmp/git-ssh.sh >>> INFO [73e91495] Finished in 0.347 seconds with exit status 0 ( >>> successful). >>> cap aborted! >>> administrator >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/net-ssh-2.7.0/lib/net/ >>> ssh.rb:215:in `start' >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/sshkit-1.1.0/lib/sshkit/backends/netssh.rb:156:in >>> >>> `ssh' >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/sshkit-1.1.0/lib/sshkit/backends/netssh.rb:68:in >>> >>> `upload!' >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/capistrano-3.0.0/lib/ >>> capistrano/tasks/git.rake:11:in `block (3 levels) in <top (required)>' >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/sshkit-1.1.0/lib/sshkit/backends/netssh.rb:42:in >>> >>> `instance_exec' >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/sshkit-1.1.0/lib/sshkit/backends/netssh.rb:42:in >>> >>> `run' >>> /Users/vmcilwain/.rvm/gems/ruby-2.0.0-p247/gems/sshkit-1.1.0/lib/sshkit/ >>> runners/parallel.rb:12:in `block (2 levels) in execute' >>> Tasks: TOP => git:check => git:wrapper >>> (See full trace by running task with --trace) >>> >>> >>> On Sunday, December 8, 2013 4:01:11 PM UTC-5, Lee Hambley wrote: >>>> >>>> Lots of stuff on capistranorb.com! >>>> >>>> On Sunday, December 8, 2013, Vell wrote: >>>> >>>>> Versions: >>>>> >>>>> - Ruby 2.0.0-p247 >>>>> - Capistrano 3.0.1 >>>>> - Rake / Rails / etc (unsure about this question. its a simple >>>>> ruby application) >>>>> >>>>> Platform: >>>>> >>>>> - Working on.... Mac OS X 10.9 >>>>> - Deploying to... Mac OS X 10.7 >>>>> >>>>> Logs: >>>>> >>>>> - I don't have any logs as of yet >>>>> >>>>> Files: >>>>> >>>>> - Capfile >>>>> - deploy.rb >>>>> - Stage files (production.rb, staging.rb) >>>>> >>>>> I have used capistrano 2 to deploy rails apps. I have not had to do >>>>> that in a long time. I am trying to deploy a simple ruby application that >>>>> I >>>>> have created using the GLI gem but I can't seem to get a handle on the >>>>> changes from capistrano 2 to capistrano 3. What happened me with >>>>> capistrano >>>>> 2 when I first started using it was this page on the capistrano github >>>>> wiki >>>>> https://github.com/capistrano/capistrano/wiki/2.x-from-the-beginning. Is >>>>> there a page like this for capistrano 3? Something detailed and step >>>>> by step that will help me understand things as I go along? >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Capistrano" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web, visit >>>>> https://groups.google.com/d/msgid/capistrano/07aa0218-f85d-469a-9f60-2544a7465401%40googlegroups.com >>>>> . >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> >>>> -- >>>> Lee Hambley >>>> -- >>>> http://lee.hambley.name/ >>>> +49 (0) 170 298 5667 >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/3d770086-0de2-42df-a9dd-b8c7ccc3014d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
