On Jan 20, 2006, at 12:40, Stefan Schwarzer wrote:
>> To make this easy, the repository should be hosted on a computer
>> that both your development machine and the production server have
>> access to. That could be the production server, or it could be
>> your development machine, provided you have the necessary outgoing
>> network privileges (proper ports opened through your firewall, for
>> example), or it could be a completely separate third machine. Then
>> you can have a working copy checked out on your development
>> machine, and another one checked out on the production server, and
>> update the production working copy as needed.
>
> Thanks for the answer. But the question then is more direct:
> - How do I checkout to my production server? Can I do this from my
> local machine? And if so how does the command - some sort of ssh
> +svn look like?
From your local machine, you would connect to the remote machine
using ssh. You need an ssh client on your local machine, and an ssh
server running on the production machine. ssh clients and servers are
built into Mac OS X / Linux / Unix / *BSD and similar operating
systems. For Windows, "PuTTY" is a popular ssh client, but I'm not
sure if any ssh servers are available (or possible).
> - Or is the only solution to install subversion on the production
> server to grep the repository from there? And if so how does the
> command - some sort of ssh+svn look like?
Yes, you would need to install the Subversion client on the
production machine. You don't need to run the Subversion server there
unless you've decided to make the production server also host your
Subversion repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 20 14:45:56 2006