May 7, 201016 yr Folks, Anyone care to give me a dummies guide on how to use Tortoise SVN. I have a project hosted on sourceforge and just want to upload a couple of files to start it off. Atm I have the files in a folder on my localhost
May 7, 201016 yr Sounds quite straight forward. Bear in mind I've never used SourceForge before, but this applies to pretty much all SVN repositories anyway. 1) You need a working copy of the repository on SourceForge. You should have an SVN URL and username/password on SourceForge. To create working copy: on your PC, right-click where you want to checkout the working copy to (a subfolder in your htdocs dir?) and select "SVN Checkout". 2) Enter the URL, and enter your login details where prompted. 3) You'll end with a working copy of your project from SourceForge 4) Now copy in the files you want to upload to this working copy folder 5) Right-click in the working copy select "SVN Commit" 6) Enter a log message to describe the changes you've made and then submit Your files should now be in your SourceForge repository SourceForge.net provides SVN access both to project members (developers) and to the community (non-developers). Developers are listed as members of the project. Developers access the project SVN repository via HTTPS authentication, allowing them to perform write operations. Users who attempt a developer operation will be prompted for their username and password. If incorrect, or permissions are not set to allow the user access, the operation will be denied. Project developers should use the same password as used for authentication to the SourceForge.net website, when prompted for one. It is within the discretion of the project administrator to grant SVN write access to project developers. These permissions are shown on the summary page of the Project Admin pages (which may be accessed by all project members). Basically, your username/password are the same as your SourceForge.net login. If someone doesn't have login credentials then [depending or your settings] they'll either be refused access, or they'll be able to checkout a read-only version
May 7, 201016 yr I've used it various times for a few WordPress plugins I've developed, and I've still not totally got my head around it!
May 7, 201016 yr You probably know this already and when you begin to understand the idea of svn you'll start to understand how to use it effectively. SVN is a version control software. SVN is a must when multiple people are working on the same piece of software. Common/default layout of a svn server: branch/ - (there can be many branches) A copy of the trunk/ from a certain point, usually used when a developer wants to go off on their own and work on, say a big feature such as a "forum" - once completed this will usually be MERGED into the trunk/ tags/ - (there can be many tags) People get confused with this one as it works exactly the same as branch functionality - think of it this way though: tags are snapshots of the development.. or milestones. If i want to release beta I'd whack it in tags/, if i release version 1.5 I'd tag it.) trunk/ - The folder which contains all changes from the start of the project to the latest commits. This will contain all of the fixes etc applied - in most cases will be unstable code. Hopefully that clears things up.. I'm not great at explaining things :/
May 10, 201016 yr Author Do I have to create these folders in sourceforge? I cant get my head around using it :facepalm:
Create an account or sign in to comment