subversion questions

[Nrupen Kantamneni <np...@cypress.com>]

I have a few questions on subversion.

1.       Can we have revision control via web browser based ? If yes can you provide me the settings

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)



Thanks,
Nrupen


________________________________
This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.

Re: subversion questions

[Les Mikesell <le...@gmail.com>]

On Tue, Nov 1, 2011 at 10:41 AM, Nrupen Kantamneni <np...@cypress.com> wrote:
> Thanks for the option.Is there any way to tell the tool to prompt the user whether he needs to checkin (something like SVNAutoversioning prompt) instead of making it default?

I'm curious about this use case.  Is the DeltaV/WebDAV capability
present on many platforms where you can't run a subversion client?
And would you really use svn versioning on a single office document
where a more useful internal versioning/markup capability is already
available? Svn seems like a better fit for a project directory of
mostly-text files.

-- 
  Les Mikesell
     lesmikesell@gmail.com

RE: subversion questions

[Nrupen Kantamneni <np...@cypress.com>]

Thanks for the option.Is there any way to tell the tool to prompt the user whether he needs to checkin (something like SVNAutoversioning prompt) instead of making it default?



-----Original Message-----
From: Philip Martin [mailto:philip.martin@wandisco.com]
Sent: Tuesday, November 01, 2011 8:53 PM
To: Nrupen Kantamneni
Cc: Ryan Schmidt; users@subversion.apache.org
Subject: Re: subversion questions

Nrupen Kantamneni <np...@cypress.com> writes:

> Now from my mobile browser, I should be able to upload a document to
> the server after downloading the file and making changes. That would
> be more convenient for me to manage the files from where ever I am.
> Hope I am clear in clarifying my use model

Perhaps autoversioning:
http://svnbook.red-bean.com/nightly/en/svn.webdav.autoversioning.html

--
Philip

This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.

Re: subversion questions

[Philip Martin <ph...@wandisco.com>]

Nrupen Kantamneni <np...@cypress.com> writes:

> Now from my mobile browser, I should be able to upload a document to
> the server after downloading the file and making changes. That would
> be more convenient for me to manage the files from where ever I am.
> Hope I am clear in clarifying my use model

Perhaps autoversioning:
http://svnbook.red-bean.com/nightly/en/svn.webdav.autoversioning.html

-- 
Philip

RE: subversion questions

[Nrupen Kantamneni <np...@cypress.com>]

Lets look at it this way
I use SVN for my version control/central repository to share the same file with multiple people at the same time.
Assume that it is a Microsoft documents that needs to be accessed.

Now from my mobile browser, I should be able to upload a document to the server after downloading the file and making changes. That would be more convenient for me to manage the files from where ever I am.
Hope I am clear in clarifying my use model

-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2011a@ryandesign.com]
Sent: Tuesday, November 01, 2011 6:08 PM
To: Nrupen Kantamneni
Cc: users@subversion.apache.org
Subject: Re: subversion questions


On Nov 1, 2011, at 07:25, Nrupen Kantamneni wrote:

> I would like to be able to at least check in,checkout files  via web.

There isn't really such a thing as "check out" in Subversion. "Check out" really just means "get". And you can "get" (i.e. look at or download) any files you want via the web interface.

"Check in", what we usually call "commit", isn't something I'm aware of any web interface letting you do. That doesn't mean nobody's made it, I'm just not aware of anyone having made it yet. You could make such an interface yourself if you really wanted to and were good with web programming. But I'm not clear on the use case.

What kinds of files would you want to be able to change via a web interface? People often use Subversion to develop the source code of an application or of a web site, and such files typically do not stand alone; they're part of a whole, and need to be tested as a whole. That's why the usual workflow is that you check out a working copy of the whole project to your computer; make changes to files in the working copy, often to several different files in order to implement a single conceptual change; test that change by building the program and running it locally on your computer, or by accessing the web site running on your local web server; and finally, when everything is correct, commit the change to the repository.

If this does not describe your desired workflow, how does yours differ?



This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.

Re: subversion questions

[Ryan Schmidt <su...@ryandesign.com>]

On Nov 1, 2011, at 07:25, Nrupen Kantamneni wrote:

> I would like to be able to at least check in,checkout files  via web.

There isn't really such a thing as "check out" in Subversion. "Check out" really just means "get". And you can "get" (i.e. look at or download) any files you want via the web interface.

"Check in", what we usually call "commit", isn't something I'm aware of any web interface letting you do. That doesn't mean nobody's made it, I'm just not aware of anyone having made it yet. You could make such an interface yourself if you really wanted to and were good with web programming. But I'm not clear on the use case.

What kinds of files would you want to be able to change via a web interface? People often use Subversion to develop the source code of an application or of a web site, and such files typically do not stand alone; they're part of a whole, and need to be tested as a whole. That's why the usual workflow is that you check out a working copy of the whole project to your computer; make changes to files in the working copy, often to several different files in order to implement a single conceptual change; test that change by building the program and running it locally on your computer, or by accessing the web site running on your local web server; and finally, when everything is correct, commit the change to the repository.

If this does not describe your desired workflow, how does yours differ?

RE: subversion questions

[Nrupen Kantamneni <np...@cypress.com>]

Hi Ryan,

I would like to be able to at least check in,checkout files  via web.


-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2011a@ryandesign.com]
Sent: Tuesday, November 01, 2011 5:48 PM
To: Nrupen Kantamneni
Cc: users@subversion.apache.org
Subject: Re: subversion questions


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.





This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.

Re: subversion questions

[Ryan Schmidt <su...@ryandesign.com>]

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.