subversion
Installing Subversion on Mac OS X Server
I have first installed Fink a programm of the Fink project that enables the easy deployment of unix-based open source software on a Mac OS X Server (http://www.finkproject.org/download/). Then with Fink I downloaded a SVN server. A good description can be found at oReilly blog (http://www.devdaily.com/blog/post/mac-os-x/installing-subversion-svn-ser...). I created as admin the SVNRepository in the root directory and defined one user "jdorn" with a password in the file passwd.
With "sudo -u www /sw/bin/svnserve -d -r /SVNRepository" I have started the SVN server.
I have downloaded svnx from the apple download side as a client.
http://www.wikihow.com/Install-Subversion-on-Mac-OS-X
SVN uses port 3690 and I added the port in the router software.
Now the server can be accessed at svn://techscreen.tuwien.ac.at.
Taggings:
How to setup Subversion and Trac app on a Debian/Apache server
As of (almost) anything there's also a good howto on the Web for that.
Here are the basic/central steps to take.
- Install the required packages.
sudo aptitude install enscript libapache2-mod-python python-docutils trac db4.3-util libapache2-svn subversion-tools - Create a virtual host dir for SVN.
sudo mkdir -p /var/local/www/svn/svn.example.com - Create a development group, and add the web user to it.
sudo addgroup example; sudo adduser www-data example - Add users to the development group. These are persons that need access to the repository.
sudo adduser username1 example
sudo adduser username2 example
sudo adduser username3 example
... - Set proper permissions.
sudo chmod 2770 /var/local/www/svn/svn.example.com - Set up the repository.
sudo svnadmin create /var/local/www/svn/svn.example.com - Clear the current password file (we'll be using HTTPS).
sudo rm /var/local/www/svn/svn.example.com/conf/passwd
sudo touch /var/local/www/svn/svn.example.com/conf/passwd - Allow the group to write to the repository.
sudo chmod -R g+w /var/local/www/svn/svn.example.com - Set proper file ownership.
sudo chown -R www-data:example /var/local/www/svn/svn.example.com - Set the repository access permissions. (see)
sudo vi /var/local/www/svn/svn.example.com/conf/authz - Create a dir for the log files.
sudo mkdir /var/log/apache2/svn.example.com - Add the site to the log rotation list.
sudo vi /etc/logrotate.d/apache2 - Configure the virtual host.
sudo vi /etc/apache2/sites-available/svn.example.com
# Subversion Configuration
<VirtualHost [server's IP address]:80>
ServerName svn.example.com
Redirect / https://svn.example.com/
</VirtualHost>
<VirtualHost [server's IP address]:443>
ServerName svn.example.com
<Location />
DAV svn
AuthType Basic
AuthName "svn.example.com"
AuthUserFile /var/local/www/svn/svn.example.com/conf/passwd
AuthzSVNAccessFile /var/local/www/svn/svn.example.com/conf/authz
SVNPath /var/local/www/svn/svn.example.com
Require valid-user
</Location>
CustomLog /var/log/apache2/svn.example.com/access.log combined
ErrorLog /var/log/apache2/svn.example.com/error.log
SSLEngine on
SSLCertificateFile /etc/apache2/ssl/apache.pem
# Add this once there is a real (non self-signed) certificate.
# SSLCertificateKeyFile /etc/apache2/ssl/server.key
</VirtualHost> - Enable the subversion virtual host.
sudo a2ensite svn.example.com - Create user/password combinations.
sudo htpasswd /var/local/svn/svn.example.com/conf/passwd username - Reload the Web server conf.
sudo /etc/init.d/apache2 reload
- Create the Web dir.
sudo mkdir -p /var/local/www/trac/trac.example.com - Set proper permissions.
sudo chmod 2770 /var/local/www/trac/trac.example.com - Create a Trac instance.
sudo trac-admin /var/local/www/trac/trac.example.com initenv - Set proper ownership on the Web dir.
sudo chown -R www-data:example /var/local/www/trac/trac.example.com - Allow the group to write to the repository.
sudo chmod -R g+w /var/local/www/trac/trac.example.com - Configure it.
sudo vi /var/local/www/trac/trac.example.com/conf/trac.ini - Create a dir for the log files.
sudo mkdir /var/log/apache2/trac.example.com - Add the site to the log rotation list.
sudo vi /etc/logrotate.d/apache2 - Configure the virtual host...
sudo vi /etc/apache2/sites-available/trac.example.com
# Trac Configuration
<VirtualHost [server's IP address]:80>
ServerName trac.example.com
Redirect / https://trac.example.com/
</VirtualHost>
<VirtualHost [server's IP address]:443>
ServerName trac.example.com
DocumentRoot /var/local/www/trac/trac.example.com/
Alias /trac/ /usr/share/trac/htdocs
<Directory "/usr/share/trac/htdocs/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
<Location />
SetHandler mod_python
PythonHandler trac.web.modpython_frontend
PythonInterpreter main_interpreter
PythonOption TracEnv /var/local/www/trac/trac.example.com/
PythonOption TracUriRoot /
AuthType Basic
AuthName "trac.example.com"
# Use the SVN password file.
AuthUserFile /var/local/svn/svn.example.com/conf/passwd
Require valid-user
</Location>
CustomLog /var/log/apache2/trac.example.com/access.log combined
ErrorLog /var/log/apache2/trac.example.com/error.log
SSLEngine on
SSLCertificateFile /etc/apache2/ssl/apache.pem
# Add this once there is a real (non self-signed) certificate.
# SSLCertificateKeyFile /etc/apache2/ssl/server.key
</VirtualHost> - Enable the Trac virtual host.
sudo a2ensite trac.example.com - Configure Trac permissions.
sudo trac-admin /var/local/www/trac/trac.example.com - Restart the Web server.
sudo /etc/init.d/apache2 restart
Have fun! :-)
Exchanging code over Internet
I dont know exactly what you mean by "secure" host, but
http://www.sourceforge.net and
http://www.assembla.com
offer both good platforms for cvs or svn repository, bug tracking and other stuff. If you interpret secure as non-public, assembla offers private password protected repositorys. I'm not sure if sourceforge supports this as well.
For quick exchange of small code pieces http://www.rafb.net is a good ressource.
Taggings:
Setting up a Subversion repository and corresponding Trac app on a (Debian/Apache) server
So the basic problem here is how to best work together productively in a programming/development project and the question which are good tools providing capabilities to potentially support and improve this.
One such tool is a version control systems (VCS) which basically helps to keep the code and especially its progress under (version) control in a code repository (transparently).
A specific such VCS is Subversion (a.k.a. SVN). This is at the time one of the most popular and up-to-date systems of its kind (i.e., centralized VCS). Its basic slogan is "CVS done right" (which consequently can be seen as Subversion's indirect predecessor system).
There are many tools available to work with Subversion from a client/user perspective like stand-alone client apps, integration in editors, e.g., via special plugins or also complete integration in a full-blown IDE (integrated development environment).
Now, what's up to do is to actually setup a Subversion system on a server and to create a code repository for a programming/development project. In this case a Debian-based OS with an Apache Web server is chosen as infrastructure.
Additionally a Trac app should be installed which among other things offers nice and convenient Web visualization of the code repository (and its progress) to users.
When all this is in place users can take the benefits of using Subversion for version control of the code of the project.
