When we are working using Subversion, we can expose the Subversion repository using svnserve (open the default port 3690 and svn:// protocol) or leverage the Apache WebDav to expose your Subversion service in HTTP (the web protocol -- I've always tempted to write it as HTTP Protocol which is incorrect as the last P letter stands for 'protocol').
And of course if you are just as lazy as I, you will use the CollabNet Subversion or Edgewall Trac.
Mercurial Server from Lshift is one way to achieve similar thing. Though it is named Mercurial Server, it is not a server in traditional client/server perspective. It leverages the SSH authentication to make it like a central repository where multiple user can access and serves the same purpose.
Surprisingly, it is very easy to install in an Ubuntu box.
[sourcecode lang="shell"]
$ sudo apt-get install mercurial-server
[/sourcecode]
Gotcha! You have it now.
With this Mercurial Server, you can access the server using:
hg clone ssh://<ssh-user>@<host-name-or-ip-address>[:<ssh-port-num>]/<folder>
[sourcecode lang="shell"]
$ hg clone ssh://mercurial@192.168.0.1/projects
[/sourcecode]
Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts
Monday, June 14, 2010
Wednesday, March 17, 2010
Installation of Hudson in Karmic Koala (Ubuntu 9.10)
We are implementing Hudson continuous integration server heavily. Initially we are running all our Hudson jobs on a Windows box.
Hudson is an open source continuous integration tool. It gains popularity very fast and based on my experience in production, it is one of the most active open source project component I have been using. It is pretty common to get Hudson updates more than once a week.
With support from Debian community which setup the Hudson installer which updates easily through the apt tools, I became enticed to move to Ubuntu. I was following the instructions from the Hudson CI site.
These steps show how easy it is to deploy Hudson in an Ubuntu box.
[sourcecode lang="shell"]<br />$ wget -O - http://hudson-ci.org/debian/hudson-ci.org.key | sudo apt-key add -<br />[/sourcecode]
Add this entry to your /etc/apt/sources.list using your favorite editor.
[sourcecode lang="shell"]<br />$ sudo vi /etc/apt/sources.list<br />[/sourcecode]
Add this line at the end:
[sourcecode lang="shell"]<br />deb http://hudson-ci.org/debian binary/<br />[/sourcecode]
Then run the apt tool to update your Debian packages.
[sourcecode lang="shell"]<br />$ sudo apt-get update<br />$ sudo apt-get install hudson<br />[/sourcecode]
Upon finishing the whole thing, I popped out a browser and hit the URL: http://localhost:8080/, and YES! it works!
Thursday, September 18, 2008
Failed to install varnish in Ubuntu
Today I tried to install SCons on my VirtualBox Ubuntu. It gave an error because my previous installation of varnish on this Ubuntu failed, so every time I invoke the apt-get install, it will try to install the varnish again and repeat the same failure. The failure is revolved around the inavailability to the crti.o library.
It seems that I'm not alone. Somebody else had failed installing varnish on Ubuntu and had the same problem.
I found out that the cause of the problem is the lacking of libc6-dev in my Ubuntu installation.
The fix to this problem turned out to be just installing the Ubuntu package libc6-dev.
The varnish installation needs the SHMEM library related to the existence of the crti.o object file in the C library (seems that it is a kernel specific library).
$ sudo apt-get install libc6-dev
or
$ sudo aptitude install libc6-dev
The package manager will choose the most suitable c library for your Ubuntu kernel.
Voila, it works!
When the failed pending varnish installation has been cleared, the uninstall feature (apt-get remove varnish) back into action again! I could install/reinstall varnish again.
Subscribe to:
Posts (Atom)