According to the comments section in this blog post MediaTemple has
their own capistrano deploy script:
The problem is that this deploy script refers to a file called
'mt-capistrano' that I can't find anywhere.
Does anyone have any suggestions for deploying to MediaTemple? With
the way the container is setup it looks like I can't use my
traditional deployment script.
Thanks :)
--
John Kopanas
jo...@kopanas.com
http://www.kopanas.com
http://www.cusec.net
http://www.soen.info
gem install mt-capistrano --source=http://gems.mediatemple.net/
Micah
which is triggered by line 23 in subversion.rb (which in turn calls
svn_log on line 81), which uses:
`svn log -q --limit 1 #{path}`
Running "svn --version" tells me MediaTemple is running Subversion
1.1.4. I doubt if this version supports the limit switch for the "svn
log" command (how to tell?). Runnning this command locally runs without
problems...
Any ideas to resolve this? It'll be highly appreciated, since I'm
stuck! :)
PS: Why isn't Capistrano using "svn info" to determine the revision
number in the first place? Seems just a tad cleaner to me, but then
again, I'm just a n00b. :)
bye!
--
/**
* dagi3d v4 | http://dagi3d.net
*/
And how did you upgrade your Subversion on MediaTemple?
Judging from MediaTemple's deployment recipe on
http://gems.mediatemple.net/deploy.rb
they DO want me to use Subversion on the GridServer.
You seem to have plenty of ideas!
If you remove the "--limit 1" part of the svn_log command, you'll get
the same result, you just get it more slowly.
If you want to use svn info, you could modify the match to match the
revision from the output. A minimally invasive change would add a new
svn_info method:
def svn_info(path)
`svn info #{path}`
end
and then modify the match on line 23 of subversion.rb
match = svn_info(".").scan(/Revision: (\d+)/).first or
--
Ray