Hmmm and I've just noticed - my sql database is on the dreamhost
server at mysql.xxxxxxxxx.com - could this be causing a problem?
On Mar 22, 4:08 pm, "Kev" <[EMAIL PROTECTED]> wrote:
> Thanks for the help so far! I've managed to get everything up on
> mydreamhostsvn (there must have been a problem with my router at home,
> as I'm on another wireless point and have uploaded fine using the nuby
> on rails tips ...
>
> Keith - I didn't know that the svn repository needed to be the same
> name as the original name you generated the rails app with? I've
> changed my deploy.rb as follows
>
> set :user, 'xxxxxxxxx'
> set :application, "www.xxxxxx.com"
> #set :repository, "file:///home/#{user}/svn/#{application}"
> # NOTE: If file:/// doesn't work for you, try this:
> set :repository, "svn+ssh://home/#{user}/svn/mint"
>
> role :web, application
> role :app, application
> role :db, application, :primary => true
>
> set :deploy_to, "/home/#{user}/mint"
> # set :svn, "/path/to/svn" # defaults to searching the PATH
> set :use_sudo, false
>
> desc "Restart the FCGI processes on the app server as a regular user."
> task :restart, :roles => :app do
> run "#{current_path}/script/process/reaper --
> dispatcher=dispatch.fcgi"
> end
>
> Although I have kept the application name the same, I've changed the
> deploy_to location to match the original name of the rails app, but
> when the web/app/db roles are set to the name of the rails app I get a
> cannot connect error.
>
> I've renamed the application location on the server to match the
> original name of the rails app ("mint") and now the ... do I need to
> create thesymlinkmyself? My current error when running cap migrate
> is
>
> * executing task migrate
> * executing "cd /home/xxxxxx/mint/current && rake
> RAILS_ENV=production db:migrate"
> servers: ["www.xxxxxxxx.com"]
> Password:
> [www.xxxxxx.com] executing command
> ** [out ::www.xxxxxxx.com] bash: line 1: cd: /home/xxxxxxxx/mint/
> current: No such file or directory
> command finished
> command "cd /home/xxxxxxx/mint/current && rake RAILS_ENV=production
> db:migrate" failed onwww.xxxxxxxx.com
>
> It just seems like thesymlinkisn't playing nice!
>
> Jamis - Thanks for the help here, on top of how much help I've already
> received from your excellent blog!
>
> On Mar 22, 2:32 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:
>
> > Kev,
>
> > Note that, unless you are using a third-party Capistrano extension,
> > Capistrano 1.4.1 and earlier do not support local svn repositories.
> > The repository must be accessible by both the local host, and the
> > remote host. If you need to deploy from a local repository, or (in
> > general) a repository that the remote host cannot access, you might
> > want to check out the custom subversion module that wolfmanjm has
> > written for Capistrano. You should be able to search this group to
> > find references to it.
>
> > - Jamis
>
> > On Mar 22, 2007, at 5:12 AM, Kev wrote:
>
> > > Trying to deploy my first rails app todreamhostusing subversion and
> > > capistrano and I'm having a nightmare!
>
> > > I've been using bothhttp://wiki.dreamhost.com/index.php/Capistrano
> > > andhttp://nubyonrails.topfunky.com/pages/shovel_dreamhosttowalk me
> > > through, but every single step has been a horrible obstacle.
>
> > > I've created a svn repository locally (as it kept hanging when trying
> > > to create it online) and checked it out locally. I'm now working from
> > > that directory, and my deploy.rb looks like this
>
> > > set :user, 'xxxxxxx'
> > > set :application, "www.xxxxxxx.com"
>
> > > set :repository, "file:///Users/Kev/Rails/svn/#{application}"
> > > # NOTE: If file:/// doesn't work for you, try this:
> > > #set :repository, "svn+ssh://home/#{user}/svn/mint"
>
> > > role :web, application
> > > role :app, application
> > > role :db, application, :primary => true
>
> > > set :deploy_to, "/home/#{user}/#{application}"
> > > # set :svn, "/path/to/svn" # defaults to searching the PATH
> > > set :use_sudo, false
>
> > > desc "Restart the FCGI processes on the app server as a regular
> > > user."
> > > task :restart, :roles => :app do
> > > run "#{current_path}/script/process/reaper --
> > > dispatcher=dispatch.fcgi"
> > > end
>
> > > desc "Remove the 'current' thatdreamhostleaves lying around" #this
> > > is here after everything else had failed
> > > task :after_setup do
> > > delete "#{current_path}", :recursive => true
> > > end
>
> > > I can do cap setup fine, but then when I go to do cap deploy I get the
> > > following error
>
> > > [www.xxxxxxx.com] executing command
> > > ** [out ::www.xxxxxxx.com] bash: line 1: cd: /home/xxxxxx/
> > >www.xxxxxx.com/current:Nosuch file or directory
> > > command finished
> > > command "cd /home/xxxxxx/www.xxxxxx.com/current&&rake
> > > RAILS_ENV=production db:migrate" failed onwww.xxxxxx.com
>
> > > It seems as if thesymlinkis not being created ... At what stage does
> > > capistrano create the symbolic link? At setup or migrate? Because it's
> > > doing neither for me and when I try to run capsymlinkI get
>
> > > Password:
> > > [www.xxxxxxx.com] executing command
> > > command finished
> > > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/
> > > configuration.rb:226:in `join': can't convert nil into String
> > > (TypeError)
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/configuration.rb:226:in `release_path'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/actor.rb:560:in `send'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/actor.rb:560:in `method_missing'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/actor.rb:411:in `current_release'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/recipes/standard.rb:128:in `load'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/actor.rb:159:in `instance_eval'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/actor.rb:159:in `symlink'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/cli.rb:268:in `send'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/cli.rb:268:in `execute_recipes!'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/cli.rb:268:in `each'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/cli.rb:268:in `execute_recipes!'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/cli.rb:239:in `execute!'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/
> > > capistrano/cli.rb:12:in `execute!'
> > > from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/bin/
> > > cap:11
> > > from /usr/local/bin/cap:18:in `load'
> > > from /usr/local/bin/cap:18
>
> > > Could this be the root of the problem? I've already tried leaving the
> > > after_setup task from deploy, in fact that was only added after I'd
> > > spent a day trying to get it to work unsuccessfully. Any help is
> > > greatly appreciated!
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
