How to Add User to SVN? කොහොමද SVN එකට පරිෂීලකයෙක් එකතු කරන්නෙ.?

Lot of open source and commercial projects are working on the version control system like SVN,CVS.These days i was tried to configure CVS in my company local server(Linux-Fedora Core).For that purpose, i was searched lot of article about the CVS configuration but couldn't find any good article about "How to add user to SVN" but finally i did it completely.I write down it because it may be helpful to others.

Step 1.
check your CVS folder
#echo $CVSROOT

step 2.
It is possible to have cvs users which are not part of the OS (no local users). This is actually probably wanted too from the security point of view. Simply add a file named passwd (in the CVSROOT directory) containing the users login and password in the crypt format. This is can be done with the apache htpasswd tool.
Note: This passwd file is the only file which has to be edited directly in the CVSROOT directory. Also it won't be checked out. More info with htpasswd --help

# htpasswd -cb passwd prabath password1 # -c creates the file
# htpasswd -b passwd chandima password2

Step 3.
First check who is initiate you're SVN server.Ex:- cvs
Now add :cvs at the end of each line to tell the cvs server to change the user to cvs (or whatever your cvs server is running under). It looks like this:

# cat passwd
prabath:xsFjhU22u8Fuo:cvs
chandima:vnefJOsnnvToM:cvs

setp4.
change passwd file ownership to the svn user.
ex:-
chown cvs /usr/local/cvsroot

step5.
Test the login as normal user (for example here me)

# cvs -d :pserver:prabath@192.168.50.254:/usr/local/cvs login
Logging in to :pserver:prabath@192.168.50.254:2401/usr/local/cvs
CVS password:

පලමු අදියර

Comments

How to enable proxy service security in ESB 4.9.0?

Security is one of the major concern when we developing API base integrations or application developments. WSO2 supports WS Security , WS-Policy and WS-Security Policy specifications. These specifications define a behavior model for web services. Proxy service security requirements are different from each others. WSO2 ESB providing pre-define commonly used twenty security scenarios to choose based on the security requirements. This functionality is provided by the security management feature which is bundled by default in service management feature in ESB. This configuration can be done via the web console until ESB 4.8.1 release, but this has been removed from the ESB 4.9.0. Even though this feature isn't provided by the ESB web console itself same functionality can be achieved by the new WSO2 Dev Studio . WSO2 always motivate to use dev studio to prepare required artifacts to the ESB rather than the web console. Better way to explain this scenario is by example. Following

How to preserving HTTP headers in WSO2 ESB 4.9.0 ?

Preserving HTTP headers are important when executing backend services via applications/middleware. This is because most of the time certain important headers are removed or modified by the applications/middleware which run the communication. The previous version of our WSO2 ESB, version 4.8.1, only supported “ server ” and “ user agent ” header fields to preserve with, but with the new ESB 4.9.0, we’ve introduced a new new property ( http.headers.preserve ) for the passthru ( repository/conf/ passthru-http.properties ) and Nhttp( repository/conf/ nhttp.properties ) transporters to preserve more HTTP headers. Passthru transporter – support header fields Location Keep-Alive Content-Length Content-Type Date Server User-Agent Host Nhttp transport – support headers Server User-Agent Date You can specify header fields which should be preserved in a comma-separated list, as shown below. http.headers.preserve = Location, Date, Server Note that

How to monitor the Thread CPU usage in the WSO2 Products?

1. Download JConsole topthreads Plugin. 2. Add following entries to the PRODUCT_HOME/bin/wso2server.sh -Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=PORT \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Djava.rmi.server.hostname=IP_ADDRESS \ Define your IP_ADDRESS address and PORT (port should be not used anywhere in that instance) 3. Run the JConsole using following command. jconsole -pluginpath PATH_TO_JAR/topthreads-1.1.jar 4. Copy "JMXServerManager JMX Service URL" from the wso2carbon logs after restart the Wso2 Server (Eg:- service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi) to the Remote process with the username and password. 5. Under Top Threads tab you can monitor the thread CPU usage.

PRABATH'S TECH BLOG

Search This Blog