103
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 49:
Line 49: − <br><br>+ Line 72:
Line 72: + + − * To work with your repository you need to use a client like TortoiseSVN for Windows or RabbitVCS for Linux. ALso possible to use the command line with the svn command. You just import your code to <nowiki>https://server-name/repository-name/trunk</nowiki>+ + + + + + +
→Usage
* If you don't want to remember to set it manually on every file you add, you can enable the "automatic MIME type" feature. This can automatically set the line ending (for text files) or MIME type (for binary files) based on file extensions.
* If you don't want to remember to set it manually on every file you add, you can enable the "automatic MIME type" feature. This can automatically set the line ending (for text files) or MIME type (for binary files) based on file extensions.
* Be careful when setting permissions for reading and writing to a repository. When no selections are made in both the "read-only access" lists, or both the "full access" lists, they will default to 'Everyone'. To completely restrict access to specific groups and users, you must make a selection from both the "read-only access" and the "full access" lists, for either one or more groups, or one or more users.
* Be careful when setting permissions for reading and writing to a repository. When no selections are made in both the "read-only access" lists, or both the "full access" lists, they will default to 'Everyone'. To completely restrict access to specific groups and users, you must make a selection from both the "read-only access" and the "full access" lists, for either one or more groups, or one or more users.
<br>
Next procedure is to create the recommended folder structure in your repository with this command in a terminal
Next procedure is to create the recommended folder structure in your repository with this command in a terminal
<nowiki>svn mkdir https://server-name/repository-name/{branches,tags,trunk} -m "Recommended structure"</nowiki>
<nowiki>svn mkdir https://server-name/repository-name/{branches,tags,trunk} -m "Recommended structure"</nowiki>
Tags are, like branches, copies of your code. Tags, however, are not to be used for active development. They mark (tag) a certain state your code is in for exampel when you release your code.
Tags are, like branches, copies of your code. Tags, however, are not to be used for active development. They mark (tag) a certain state your code is in for exampel when you release your code.
<br>
The essential Subversion lifecycle is the following:
# Check out a project (a directory path) from a repository.
# In that project directory, create or edit files and subdirectories.
# Update your local copy from the repository, picking up changes your team members may have made since your last update.
# Go to step 2. If you're ready to commit your changes, go to step 5.
# Commit your changes to the repository. Go to step 2.
<br>
To work with your repository you need to use a client like TortoiseSVN for Windows or RabbitVCS for Linux. ALso possible to use the command line with the svn command. You just import your code to <nowiki>https://server-name/repository-name/trunk</nowiki>
=== Additional information ===
=== Additional information ===
