A tutorial about CVSNT, a concurrent versions system. How to backup the CVS repository. Includes examples. EVS is an advanced multiplatform version control ecosystem. Supporting many advanced features it remains compatible with industry standard protocols. The CVSNT Versioning System implements a version control system: it keeps track of all . “CVSNT Auditing Tutorial”. Bo Berglund. Retrieved 23 March .
|Published (Last):||3 September 2004|
|PDF File Size:||13.2 Mb|
|ePub File Size:||5.83 Mb|
|Price:||Free* [*Free Regsitration Required]|
Most of the discussion is also valid for installation on Windows XP-Pro see below for an important setting. The guide uses the Innosetup based installer that I maintain but similar results can probably be obtained by using the Innosetup installer published by Oliver Giesen as well. Also make sure you are logged on as an administrator of the PC using an account with administrative cvsmt.
[cvsnt] CVS complete tutorial
Select the View tab and scroll down to the bottom tugorial you find this item. Now for the actual installation and configuration: Create CVS directories Create two directories on the target machine, c: If you have a separate disk partition to spare for CVS then use that instead. The important point here is that the disk where the repository is located on is NTFS. Directory security and permissions Give c: The cvstemp directory must NOT be located in either c: Notice that on XP-Pro out of the box from Microsoft the permissions cannot be set like this until “Simple File Sharing” is switched off see above.
So you must do this if you use XP-Pro. Installation component selection screen: Install in progress Release notes Installation done!
This is the initial screen showing that both services are running: If it is started then tutprial it. You can leave the Lock Service running. Repository creation The tab will initially look like this: Add repository Now you will add a repository to the server. This is done using the “Add” button. When you click this a dialogue shows up where you will define your repository.
Repository folder Click the ellipsis button for Location to bring up the folder browser. Now you can browse to the location you want for your repository and add a new ttorial here. Name repository Now fill in the description and the name of the repository as well. Do NOT accept the suggested name, which is the same as the folder path!
When you click Yes then the new folder will be converted to a real repository: Now the list of repositories has been populated with the first repository: You can add as many as you like almost cvstn please do not fall for the temptation to use one repository for each and every project!
There are a lot of possibilities tutodial streamline the development process tutlrial CVSNT, but many of these use the virtual modules concept and this is only possible within a single repository. Server Settings Now go on to the Server Settings tab. Here the default settings are all right for now, except the Temporary Directory setting. CVSNT will strip the domain part from all cgsnt that log on using the default domain before processing.
The result of this is that all users that “belong” to the domain specified in this box will be logged using only the account name, likewise these usernames will be supplied to the administrative scripts without the domain name. All others will have a domain name added.
This must be accounted for in any admin script used. Use the ellipsis button to browse for the folder prepared for this purpose above: Compatibility On the next tab Compatibility Options there is nothing you need to change for now: The sceen list the available plugins and when you select a line you will be able to configure this plugin by clicking the configure button: Please set it like this: Advanced settings The final tab on the Control Panel deals with advanced configuration settings and you need not change anything here.
Apply configuration changes Now click the Apply button! This is really importanttutoeial will happen unless you do this! Note that after you have done this the Apply button is disabled.
ccsnt After a few moments the Stop tutotial will be highlighted. Restart the server In order for you cvwnt be able to use the command line cvs you need to have the path variable set to include the location of the cvs. Since the installer will have put this into the system path variable it will work if you restart the server. You can check this by going to a command window and typing the command: This is cvsht step that is only needed if you tytorial on using the sserver or pserver protocols with this CVS server.
If your users are all on Windows PC: If you gutorial to go with sspi recommended then you can skip the discussion on how to add and manage users in this section. Creating CVS accounts on the server In order for pserver and sserver to work you have to define CVS users, but before you can do this you need to create two real accounts on the server. These accounts will be used by the CVS users as the working accounts. You need one account which will be a CVS administrative account and one which will be a normal user account.
Note that the CVS administrator need not be a server administrator! The two accounts are added through the Users dialog in Computer Management. I have used the account names cvsadmin and cvsuser as shown above. This password is only for CVS use so it should not be the real system password! Enter the password twice. CVS will not accept any user login that is not connected to a “real” account. Instead you can “alias” a CVS login to a “real” account using this command: This makes it possible to use NTFS file system permissions to tutorrial access to certain parts of the repository to some users.
You simply create a system account for which you set limited permissions and then you alias the CVS login to this user.
Note that this command will fail if there is a space embedded in the real account name! DON’T ever use spaces in these contexts!!!!!
But using quotes may solve the problem like this: You can add domain users with the following command: I cannot check it because I don’t have a domain. The server is now ready to be used and you can check the pserver functionality by doing this: Testing the CVS connection with sserver Open another command window and type: Testing the CVS connection with pserver Open another command window and type: There have been a number of reports that people have not been able to add users or execute the cvs admin command even though they were members of the Administartors group or even of Domain Admins.
In order to avoid this there is a simple way to manage who will have admin rights on the CVSNT server. Here is how to: Edit tutoiral file by adding on separate lines the login names of the users you want to give administrative priviliges on the CVS server.
The file could look like this: Only cvwnt password for login is ‘encrypted’ and this is only barely so.
[cvsnt] CVS complete tutorial
All other traffic is in cleartext To protect your data you should use the: As an alternative with the same basic functionality as pserver you can use sserver instead. This uses encrypted connections tutogial default and is probably better if you want to add cvs logins that do not correspond to real accounts see above.
This will bring up a dialogue where you can just fvsnt the checkbox to disable the protocol: Here is the full syntax for this command: When the command is executed there will be a password dialogue that asks for the password of john twice for confirmation. Once accepted the account charlie will instead be used so the password is no longer used.
If you plan on using pserver or sserver with a fairly large number of different user logins then you might want to do as follows also described above: Login to the cvs server using an admin account. Add the logins with the following command to alias to the cvsuser: You may add as many pserver users this way as you like. They will all be individually identified by the login name even though the operations on the repository will be done in the cvsuser account context.
Mail systems will recognize these user names as well see below. Limiting user access with sspi When used normally sspi will accept connections from all system users that authenticate against the system local or domain.
Often this is not really what we want, instead we want to use the same mechansism as is used with: Note that in this case there is no need for entering passwords into the passwd file, sspi uses the system login and the passwd file is only used as a list of accepted users. So simply issuing this command when logged in as a CVS administrator will work: The NTFS file system permissions can be used to tune the access to the CVS repository with more granularity than the passwd tuutorial allows.
Here is how it is done: Create a number of NT user groups where members can be ccsnt and removed easily. Don’t use aliases in the login scheme, let each user login as himself, for example using: CVSNT tries its best to handle spaces embedded in file and directory names.