[Capistrano] Re: Trouble authenticating with different svn and application servers
Set :scm_username, not :svn_username (unless you're using Capistrano 1.4.x or earlier). The variable was renamed in Capistrano 2.0 for greater consistency between different SCM's. - Jamis On Wed, Dec 3, 2008 at 4:06 PM, BarefootSanders [EMAIL PROTECTED] wrote: I'm having trouble authenticating and getting the right credentials to the right places. This is the deploy.rb file: # deploy.rb set :application, my application set :repository, my svn repo # If you aren't deploying to /u/apps/#{application} on the target # servers (which is the default), you can specify the actual location # via the :deploy_to variable: set :deploy_to, my www root # If you aren't using Subversion to manage your source code, specify # your SCM below: # set :scm, :subversion server my web host, :app, :web, :db, :primary = true set :use_sudo, false set :user, 'my ssh username' set :svn_username, 'my svn username' This is the output of cap deploy:update: Project/root$ cap deploy:update * executing `deploy:update' ** transaction: start * executing `deploy:update_code' executing locally: svn info {my svn repo}/ -rHEAD * executing svn checkout -q -r10 {my svn repo} {my deploy path}/ releases/20081203225415 (echo 10 {my deploy path}/20081203225415/ REVISION) servers: [{my application server}] Password: [{my application server}] executing command ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Password for '{MY SSH USERNAME WHICH SHOULD BE MY SVN USERNAME}': ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Username: and right after the Username prompt it throws a line break and hangs. i can ctrl+c it but that just crashes it. Other than that I cant do anything. If you notice, its using my ssh username for the svn repo. I'm hoping i can correct this and it will fix the problem. Any suggestions? Just some more info, my svn repo is an http:// url. Does that matter? I dont believe my svn host supports ssh+svn:// --~--~-~--~~~---~--~~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~--~~~~--~~--~--~---
[Capistrano] Re: Trouble authenticating with different svn and application servers
Sanders, Check your apache log - if you are using passenger mod_rails - there will be something in there, or your app logs about why it coulnd't start - Lee 2008/12/3 BarefootSanders [EMAIL PROTECTED] Ahh ok thanks. That seemed to fix it. Now i have another problem if you'd be so kind. Not exactly related but now im getting a 500 error. along with 'Rails application failed to start properly'. Any suggestions as to how to fix this? Thanks again. On Dec 3, 6:31 pm, Jamis Buck [EMAIL PROTECTED] wrote: Set :scm_username, not :svn_username (unless you're using Capistrano 1.4.x or earlier). The variable was renamed in Capistrano 2.0 for greater consistency between different SCM's. - Jamis On Wed, Dec 3, 2008 at 4:06 PM, BarefootSanders [EMAIL PROTECTED] wrote: I'm having trouble authenticating and getting the right credentials to the right places. This is the deploy.rb file: # deploy.rb set :application, my application set :repository, my svn repo # If you aren't deploying to /u/apps/#{application} on the target # servers (which is the default), you can specify the actual location # via the :deploy_to variable: set :deploy_to, my www root # If you aren't using Subversion to manage your source code, specify # your SCM below: # set :scm, :subversion server my web host, :app, :web, :db, :primary = true set :use_sudo, false set :user, 'my ssh username' set :svn_username, 'my svn username' This is the output of cap deploy:update: Project/root$ cap deploy:update * executing `deploy:update' ** transaction: start * executing `deploy:update_code' executing locally: svn info {my svn repo}/ -rHEAD * executing svn checkout -q -r10 {my svn repo} {my deploy path}/ releases/20081203225415 (echo 10 {my deploy path}/20081203225415/ REVISION) servers: [{my application server}] Password: [{my application server}] executing command ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Password for '{MY SSH USERNAME WHICH SHOULD BE MY SVN USERNAME}': ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Username: and right after the Username prompt it throws a line break and hangs. i can ctrl+c it but that just crashes it. Other than that I cant do anything. If you notice, its using my ssh username for the svn repo. I'm hoping i can correct this and it will fix the problem. Any suggestions? Just some more info, my svn repo is an http:// url. Does that matter? I dont believe my svn host supports ssh+svn:// --~--~-~--~~~---~--~~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~--~~~~--~~--~--~---
[Capistrano] Re: Trouble authenticating with different svn and application servers
hmm, this seems strange but i tried to cd into my log directory (app/ shared/log) and it says 'permission denied'?? how can that be? did i set something up wrong in capistrano? On Dec 3, 6:39 pm, Lee Hambley [EMAIL PROTECTED] wrote: Sanders, Check your apache log - if you are using passenger mod_rails - there will be something in there, or your app logs about why it coulnd't start - Lee 2008/12/3 BarefootSanders [EMAIL PROTECTED] Ahh ok thanks. That seemed to fix it. Now i have another problem if you'd be so kind. Not exactly related but now im getting a 500 error. along with 'Rails application failed to start properly'. Any suggestions as to how to fix this? Thanks again. On Dec 3, 6:31 pm, Jamis Buck [EMAIL PROTECTED] wrote: Set :scm_username, not :svn_username (unless you're using Capistrano 1.4.x or earlier). The variable was renamed in Capistrano 2.0 for greater consistency between different SCM's. - Jamis On Wed, Dec 3, 2008 at 4:06 PM, BarefootSanders [EMAIL PROTECTED] wrote: I'm having trouble authenticating and getting the right credentials to the right places. This is the deploy.rb file: # deploy.rb set :application, my application set :repository, my svn repo # If you aren't deploying to /u/apps/#{application} on the target # servers (which is the default), you can specify the actual location # via the :deploy_to variable: set :deploy_to, my www root # If you aren't using Subversion to manage your source code, specify # your SCM below: # set :scm, :subversion server my web host, :app, :web, :db, :primary = true set :use_sudo, false set :user, 'my ssh username' set :svn_username, 'my svn username' This is the output of cap deploy:update: Project/root$ cap deploy:update * executing `deploy:update' ** transaction: start * executing `deploy:update_code' executing locally: svn info {my svn repo}/ -rHEAD * executing svn checkout -q -r10 {my svn repo} {my deploy path}/ releases/20081203225415 (echo 10 {my deploy path}/20081203225415/ REVISION) servers: [{my application server}] Password: [{my application server}] executing command ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Password for '{MY SSH USERNAME WHICH SHOULD BE MY SVN USERNAME}': ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Username: and right after the Username prompt it throws a line break and hangs. i can ctrl+c it but that just crashes it. Other than that I cant do anything. If you notice, its using my ssh username for the svn repo. I'm hoping i can correct this and it will fix the problem. Any suggestions? Just some more info, my svn repo is an http:// url. Does that matter? I dont believe my svn host supports ssh+svn:// --~--~-~--~~~---~--~~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~--~~~~--~~--~--~---
[Capistrano] Re: Trouble authenticating with different svn and application servers
You should make sure your app/shared/* directories are writable by the deploy user, at least, and the app/shared/log directory is writable by the user that your application will be running as. - Jamis On Wed, Dec 3, 2008 at 4:56 PM, BarefootSanders [EMAIL PROTECTED] wrote: hmm, this seems strange but i tried to cd into my log directory (app/ shared/log) and it says 'permission denied'?? how can that be? did i set something up wrong in capistrano? On Dec 3, 6:39 pm, Lee Hambley [EMAIL PROTECTED] wrote: Sanders, Check your apache log - if you are using passenger mod_rails - there will be something in there, or your app logs about why it coulnd't start - Lee 2008/12/3 BarefootSanders [EMAIL PROTECTED] Ahh ok thanks. That seemed to fix it. Now i have another problem if you'd be so kind. Not exactly related but now im getting a 500 error. along with 'Rails application failed to start properly'. Any suggestions as to how to fix this? Thanks again. On Dec 3, 6:31 pm, Jamis Buck [EMAIL PROTECTED] wrote: Set :scm_username, not :svn_username (unless you're using Capistrano 1.4.x or earlier). The variable was renamed in Capistrano 2.0 for greater consistency between different SCM's. - Jamis On Wed, Dec 3, 2008 at 4:06 PM, BarefootSanders [EMAIL PROTECTED] wrote: I'm having trouble authenticating and getting the right credentials to the right places. This is the deploy.rb file: # deploy.rb set :application, my application set :repository, my svn repo # If you aren't deploying to /u/apps/#{application} on the target # servers (which is the default), you can specify the actual location # via the :deploy_to variable: set :deploy_to, my www root # If you aren't using Subversion to manage your source code, specify # your SCM below: # set :scm, :subversion server my web host, :app, :web, :db, :primary = true set :use_sudo, false set :user, 'my ssh username' set :svn_username, 'my svn username' This is the output of cap deploy:update: Project/root$ cap deploy:update * executing `deploy:update' ** transaction: start * executing `deploy:update_code' executing locally: svn info {my svn repo}/ -rHEAD * executing svn checkout -q -r10 {my svn repo} {my deploy path}/ releases/20081203225415 (echo 10 {my deploy path}/20081203225415/ REVISION) servers: [{my application server}] Password: [{my application server}] executing command ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Password for '{MY SSH USERNAME WHICH SHOULD BE MY SVN USERNAME}': ** [{my application server} :: err] Authentication realm: {my svn repo} repositories ** [{my application server} :: err] Username: and right after the Username prompt it throws a line break and hangs. i can ctrl+c it but that just crashes it. Other than that I cant do anything. If you notice, its using my ssh username for the svn repo. I'm hoping i can correct this and it will fix the problem. Any suggestions? Just some more info, my svn repo is an http:// url. Does that matter? I dont believe my svn host supports ssh+svn:// --~--~-~--~~~---~--~~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~--~~~~--~~--~--~---