Projects - Revision history

Martini at 20:14, 3 April 2017

2017-04-03T20:14:38Z

← Older revision		Revision as of 22:14, 3 April 2017
Line 28:		Line 28:

	===Configuring Apache for the project===		===Configuring Apache for the project===

			[[Category:Projects]]

Ktk: /* Create a new Subversion project */

2005-09-01T13:48:03Z

Create a new Subversion project

← Older revision		Revision as of 15:48, 1 September 2005
Line 9:		Line 9:
	Subversion source is stored in <tt>/data/svn/netlabs.org</tt>, the subversion repository should get the same name as the URL of the virtual host in the webserver. We create a new repository like this (as a sample we use the <tt>acpi</tt> project):		Subversion source is stored in <tt>/data/svn/netlabs.org</tt>, the subversion repository should get the same name as the URL of the virtual host in the webserver. We create a new repository like this (as a sample we use the <tt>acpi</tt> project):

	c-3po# svnadmin create /data/svn/netlabs.org/acpi		c-3po# svnadmin create --fs-type=fsfs /data/svn/netlabs.org/acpi

	We also propose to create the following three directories:		We also propose to create the following three directories:

Ktk at 19:51, 28 August 2005

2005-08-28T19:51:59Z

← Older revision		Revision as of 21:51, 28 August 2005
Line 13:		Line 13:
	We also propose to create the following three directories:		We also propose to create the following three directories:

	* <tt>/trunk</tt> - holds the main copy of the project where most development occurs%2%2%		* <tt>/trunk</tt> - holds the main copy of the project where most development occurs%2%2%2%
	* <tt>/branches</tt> - holds separate lines of development, defined by the developers		* <tt>/branches</tt> - holds separate lines of development, defined by the developers
	* <tt>/tags</tt> - holds significant versions of the project, like a release. Should be readonly		* <tt>/tags</tt> - holds significant versions of the project, like a release. Should be readonly

Ktk at 19:46, 28 August 2005

2005-08-28T19:46:50Z

New page

The early projects on netlabs.org were using CVS as revision control system, which was a great thing so far. Unfortunately there were some limitations in CVS so it was about time to switch to something new. We use a combination of [http://subversion.tigris.org/ Subversion] and [http://www.edgewall.com/trac/ TRAC] to make development easier for the developer itself.

This page should give you an overview about how project management at netlabs.org works, or at least should work ;). It is also a guide for administrating projects for the server administrators.

==Server==
Those steps are done by hand so far but we gonna script that one day...
===Create a new Subversion project===

Subversion source is stored in <tt>/data/svn/netlabs.org</tt>, the subversion repository should get the same name as the URL of the virtual host in the webserver. We create a new repository like this (as a sample we use the <tt>acpi</tt> project):

c-3po# svnadmin create /data/svn/netlabs.org/acpi

We also propose to create the following three directories:

* <tt>/trunk</tt> - holds the main copy of the project where most development occurs%2%2%
* <tt>/branches</tt> - holds separate lines of development, defined by the developers
* <tt>/tags</tt> - holds significant versions of the project, like a release. Should be readonly

Note that all files in <tt>branches</tt> and <tt>tags</tt> are just (copy-on-write) copies of the trunk tree. This schema is used by many projects and is described in more details at [http://www.developer.com/open/article.php/10930_3499816_3 developer.com]

You can create the directories like this:
c-3po# svn mkdir file:///data/svn/netlabs.org/acpi/trunk \
file:///data/svn/netlabs.org/acpi/branches \
file:///data/svn/netlabs.org/acpi/tags \
-m "Creating initial repository layout"

Now the initial project exists and we have some base layout. We can't checkout from remote yet however, first we have to configure Apache for that.

===Configuring Apache for the project===