Andrey Repin wrote:
> Greetings, Bob Archer!
>>> Fifth step is to make these changes available to public.
>>> Here is the problem.
>>> 1. Making public server another (readonly) working copy... not wise.
> BA> It
>>> 2. Continuous export's of the whole directory tree... not wise.
> BA> Projects
> BA> What about:
> BA> 3. rsync (or ant or...) from your build server or other workstation that
> BA> does have a working copy. This should be set up to exclude the .svn
> BA> files and any .template type files you might use.
> My working copy not accessible from the world :) And I need purely production
> server side solution, so I could just connect to it from anywhere and issue an
> updating command. However, this "anywhere" more often will be my home machine,
> but what about these unpredictable situations, where you loosing your server
> files (all or part of them) and need to get it back up and running as fast as
> Really, do you think I would expose my working machine to the world?
> Even my test server firewalled to the teeth. Working host even deeper inside
> my own LAN, only accessible from dark and scary tunnel in server. With
> toothy dog laid on the other end of it.
Rsync is typically used over ssh - with the command issued from the
private/firewalled side. If you can connect to the server via ssh
(perhaps even needing to establish a vpn first), rsync is a suitable
mechanism to send files there.
And by the way - your 'Reply-To: email setting makes it difficult to
respond back to the list.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-02 20:10:23 CEST