From users-return-12085-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Tue Nov 1 12:18:50 2011 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 55E3F783F for ; Tue, 1 Nov 2011 12:18:50 +0000 (UTC) Received: (qmail 21597 invoked by uid 500); 1 Nov 2011 12:18:49 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 21543 invoked by uid 500); 1 Nov 2011 12:18:49 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 21536 invoked by uid 99); 1 Nov 2011 12:18:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 12:18:49 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.67.31.100] (HELO smtprelay05.ispgateway.de) (80.67.31.100) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 12:18:40 +0000 Received: from [70.253.78.18] (helo=[192.168.7.80]) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1RLDII-0005WY-GE; Tue, 01 Nov 2011 13:18:18 +0100 Subject: Re: subversion questions Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Ryan Schmidt In-Reply-To: <869F12ED8B1C454BBAB9F5857676033C4D531A3E0D@VMBX132.ihostexchange.net> Date: Tue, 1 Nov 2011 07:18:05 -0500 Cc: "users@subversion.apache.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <869F12ED8B1C454BBAB9F5857676033C4D531A3E0D@VMBX132.ihostexchange.net> To: Nrupen Kantamneni X-Mailer: Apple Mail (2.1084) X-Df-Sender: MzY4ODE4 X-Virus-Checked: Checked by ClamAV on apache.org On Nov 1, 2011, at 05:24, Nrupen Kantamneni wrote: > 1. Can we have revision control via web browser based ? If yes = can you provide me the settings What functions do you want to make available via the web? Out of the box, if you serve your repository with Apache, you get a = web-based view of the files and directories in your repository, = including past revisions if you know what URL parameters to append. You = can customize the appearance of directory listings using an XSLT = stylesheet. If you install third-party web-based Subversion repository viewers like = Trac, WebSVN or ViewVC, you get a prettier view, including additional = functions like examining log messages and diffs, and then it doesn't = matters how your repository is served (i.e. it no longer needs to be = served by Apache; it could be served by svnserve). There are also third-party web-based Subversion administrative programs = like SVNManager that let you create users and repositories. I'm not aware of any web-based interfaces for modifying the contents of = a repository, such as creating, editing, renaming, moving or deleting = files or directories. Typically you want to make changes in a working = copy so that you can test your changes before committing them. > 2. Does SVN support hot swap replication (meaning the data is = continuously backed up on a different machine and if the original server = goes down the secondary immediately start serving as master) You can create replica servers using svnsync. These can be used purely = as offline backups, or can be made available online and used = simultaneously, as long as they are configured to be read-only. You may = only commit changes to the master repository, but you can configure the = slave repositories to automatically proxy write requests back to the = master. If the master fails, manual intervention is necessary to promote = one of the slaves to be the new master. Or if the failure of the master = is temporary and having only read access temporarily is acceptable, you = can just bring the master back up when you can, and let users read from = one of the slaves until then. Users do however need to specifically = select which server they want to connect to (whether the master or a = specific slave), so regardless of their choice, if that particular = server is down, those users will have to "svn relocate" their working = copies to another server if they need access to the repository during = the time that server is down.