Jensen, Adam wrote:
>> The way to do it is to ssh to the remote machine, and on the remote
>> machine, execute the "svn update" command in your production server's
>> working copy of your site. This requires you to have ssh access to
>> the remote machine, svn installed on the remote machine, and your
>> repository served on the Internet such that the production machine
>> can access it. It sounds like your setup doesn't meet these
>> requirements, so this solution won't work for you.
>
> Thanks; I thought it might not be possible, but I wanted to confirm just in case. I don't currently have ssh or rsync access, but I might be able to talk to our web support department about getting it; it would certainly make site updates easier.
If you can get ssh access to the production server, you don't actually need to
put your repository online (publically) to update the remote server. It is
actually quite easy to tunnel the Subversion traffic via the same ssh session
that you are using to initiate the update.
Once you get ssh access, you may want to consider using SVN::Notify::Mirror
(available from CPAN), which I wrote specifically for this purpose. It makes it
trivial to set up post-commit hooks to keep multiple sites up to date with
commits to the repository. I have explicit support for tunneling over SSH.
HTH
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-08 05:11:09 CEST