Browse SVN Online
Anonymous Subversion AccessTo view the contents of the iFolder and Simias subversion repositories you can use the ls command. svn ls https://ifolder.svn.sourceforge.net/svnroot/ifolder If you have not been given commit access to the projects, you can still check-out all of the files in the Subversion repositories for these projects through anonymous access. This can be done with the following commands: svn checkout https://simias.svn.sourceforge.net/svnroot/simias/trunk The user name and password are both anonymous. Developer Subversion AccessIf you have been given commit access to the ifolder or simias repositories, you may use all of the functionality provided by Subversion. For the full documentation on Subversion, you can visit their website at http://subversion.tigris.org. The most common things you will be doing with Subversion are importing your project, checking it out, updating your local copy with the repository and checking in changes. If your project's files are not yet in Subversion, you must start by importing your files into the repository. To do this, you should change to the topmost directory of your project's files and enter something like the following: svn import local_dir svn ssh://your-user-name@simias.svn.sourceforge.net/svnroot/ifolder/trunk In the above command, we are telling Subversion to recursively copy everything in the local_dir directory into repo_dir directory in your repository. If repo_dir does not exist it will be created. Once the project has been imported, you can do the check-out, update and check-in operations anytime you deem it appropriate. Now you can get your own private copy of all the project files in Subversion by giving the checkout command. You can do this with the following command: svn co svn ssh://your-user-name@simias.svn.sourceforge.net/svnroot/simias/trunk repo_dir would be replaced with any valid directory in the repository. The Subversion update command is used for downloading all changes that have been made to files in the Subversion repository to your local copy. If another developer has changed a file that you have also changed in your local copy, the changes will be merged together. Sometimes a merge is required but cannot be completed. This condition produces a conflict. If there are any conflicts during the update process, they will appear in the output of the command. Under almost all conditions, an update operation must be performed before a check-in operation. If you check-in before doing an update, you run the risk of overwriting someone else's changes! To perform a Subversion update, you should change to the root directory of your local copy of the project files and issue the following command: svn update At some point in time, you will want to commit the changes that you have made to your local copy of the project files. This is a multi-phased process that should be as follows:
When you are ready to commit your changes to the repository , change to any directory in your local copy of the project files and issue the following command: svn commit --message "My list of changes" This will commit all changes in the current directory and any of it's sub-directories to the remote repository. Again, Subversion has much more functionality than what is described here. We encorage you to read the documentation on their site, http://subversion.tigris.org/. Subversion on Windows with TortoiseSVNTortoiseSVN gives you the ability to perform Subversion functions directly from Windows Explorer. You can check out, update, commit, see diffs and so forth by right clicking on the file or folder. You can download TortoiseSVN from their website as http://tortoisesvn.tigris.org/. It is easy to install and use, and it works very well.
Subversion on OS XYou can download OS X packages for subversion from Metissian. If you want a gui subversion client, svnX by la chose interactive is really nice.
|
Can you link to Building iFolder (http://community.ifolder.com/ssf/a/c/p_name/ss_forum/p_action/1/binderId/1487/action/view_folder_entry/namespace/_ss_forum_/entryId/1384) somewhere in this article?