[Capistrano] Re: Having a horrible time with a first deployment

2007-03-22 Thread Keith Pitty
Kev, What's the name of your application? Whatever it is (i.e. the name you chose when you initially executed the rails command to create the directory structure), that's the name you should set :application to within config/deploy.rb. To me, it looks like you're confusing it with the

[Capistrano] Re: Having a horrible time with a first deployment

2007-03-22 Thread Jamis Buck
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

[Capistrano] Re: Having a horrible time with a first deployment

2007-03-22 Thread Kev
Thanks for the help so far! I've managed to get everything up on my dreamhost svn (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

[Capistrano] Re: Having a horrible time with a first deployment

2007-03-22 Thread Kev
Hmmm and I've just noticed - my sql database is on the dreamhost server at mysql.x.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

[Capistrano] Re: Having a horrible time with a first deployment

2007-03-22 Thread Kev
Ok, I've removed all prefixes from my application so it should not matter whether it is www.x.com or mysql.x.com . I've tried running the cap migrate as rake deploy, as that allows me to --trace. Here's the trace output - it's a little more helpful than before, but I can't make sense of