GenDBWiki/DeveloperDocumentation/CVSAccess - Revision history

Admin: 3 revisions

2011-10-26T06:16:11Z

3 revisions

← Older revision	Revision as of 08:16, 26 October 2011
(No difference)

imported>AlexanderGoesmann at 09:05, 29 June 2005

2005-06-29T09:05:29Z

← Older revision		Revision as of 11:05, 29 June 2005
Line 2:		Line 2:
	= CVS Access for GenDB Developers =		= CVS Access for GenDB Developers =

	This part of the documentation is intended for developers with direct CVS access to the GenDB source code. Reading the following paragraphs should help you to get started for working with the core system. Since all GenDB projects are managed via the General Project Management System (GPMS) you will also need access to at least one project for testing and working with the GenDB system. Please contact the GenDB mailing list ([[MailTo(gendb AT cebitec DOT uni DASH bielefeld DOT de)]]) for an account and access to a project. Of course, the following descriptions are only valid for developers working at the Bielefeld Center for Biotechnology.		This part of the documentation was moved to the [http://www.cebitec.uni-bielefeld.de/groups/brf/internal/AdminInfoGenDB internal wiki] since it is only intended for developers with direct CVS access to the GenDB source code working at the Bielefeld Center for Biotechnology.

	~~== CVS Access ==~~

	* create a working directory for CVS in your home directory, e.g. named `cvs`
	* `cd` to that directory and checkout the `bridge_install` repository: `cvs checkout bioinfo/bridge_install`

	~~You will need to checkout the following components:~~
	* projectmanagement
	* common
	* gendb
	* gendb_web - for setting up the web interface
	* gendb_gui - for working on the Gtk GUI
	* GOPArc - needed for the analysis of metabolic pathways and functional categories within GenDB
	* SEED - needed for comparative analyses

	~~== Setting up a GenDB Web-Server ==~~

	* change the configuration in `YOUR_INSTALL_DIR/gendb/share/www`
	* edit `user_conf.sh`:
	** choose a free port number that is not already used by another developer, e.g. `PORT=9000`
	** set CVS_SUBDIR relative to your HOME directory, e.g. `CVS_SUBDIR=juser/cvs`
	* login to the test web server machine: e.g. `rsh hook`
	* `cd YOUR_INSTALL_DIR/gendb_web`
	* start the Apache web server: `./apache2 [configtest] start`
	* point your favorite browser to the GenDB start page: `hook:9000/software/gendb`
	* you can find the error log on hook: 'tail -f YOUR_INSTALL_DIR/gendb_web/share/logs/gendb2.error`

	~~== Starting the GenDB Gtk GUI ==~~

imported>AlexanderGoesmann at 17:02, 19 November 2004

2004-11-19T17:02:06Z

Unknown user at 00:00, 1 January 1970

1970-01-01T00:00:00Z

New page

__NOTOC__
= CVS Access for GenDB Developers =

This part of the documentation is intended for developers with direct CVS access to the !GenDB source code. Reading the following paragraphs should help you to get started for working with the core system. Since all !GenDB projects are managed via the General Project Management System (!GPMS) you will also need access to at least one project for testing and working with the !GenDB system. Please contact the !GenDB mailing list ([[MailTo(gendb AT cebitec DOT uni DASH bielefeld DOT de)]]) for an account and access to a project. Of course, the following descriptions are only valid for developers working at the Bielefeld Center for Biotechnology.

== CVS Access ==

* create a working directory for CVS in your home directory, e.g. named `cvs`
* `cd` to that directory and checkout the `bridge_install` repository: `cvs checkout bioinfo/bridge_install`

You will need to checkout the following components:
* projectmanagement
* common
* gendb
* gendb_web - for setting up the web interface
* gendb_gui - for working on the Gtk GUI
* !GOPArc - needed for the analysis of metabolic pathways and functional categories within !GenDB
* !SEED - needed for comparative analyses

== Setting up a GenDB Web-Server ==

* change the configuration in `YOUR_INSTALL_DIR/gendb/share/www`
* edit `user_conf.sh`:
** choose a free port number that is not already used by another developer, e.g. `PORT=9000`
** set CVS_!SUBDIR relative to your !HOME directory, e.g. `CVS_SUBDIR=juser/cvs`
* login to the test web server machine: e.g. `rsh hook`
* `cd YOUR_INSTALL_DIR/gendb_web`
* start the Apache web server: `./apache2 [configtest] start`
* point your favorite browser to the !GenDB start page: `hook:9000/software/gendb`
* you can find the error log on hook: 'tail -f !YOUR_!INSTALL_DIR/gendb_web/share/logs/gendb2.error`

== Starting the GenDB Gtk GUI ==

← Older revision		Revision as of 19:02, 19 November 2004
Line 2:		Line 2:
	= CVS Access for GenDB Developers =		= CVS Access for GenDB Developers =

	This part of the documentation is intended for developers with direct CVS access to the !GenDB source code. Reading the following paragraphs should help you to get started for working with the core system. Since all !GenDB projects are managed via the General Project Management System (!GPMS) you will also need access to at least one project for testing and working with the !GenDB system. Please contact the !GenDB mailing list ([[MailTo(gendb AT cebitec DOT uni DASH bielefeld DOT de)]]) for an account and access to a project. Of course, the following descriptions are only valid for developers working at the Bielefeld Center for Biotechnology.		This part of the documentation is intended for developers with direct CVS access to the GenDB source code. Reading the following paragraphs should help you to get started for working with the core system. Since all GenDB projects are managed via the General Project Management System (GPMS) you will also need access to at least one project for testing and working with the GenDB system. Please contact the GenDB mailing list ([[MailTo(gendb AT cebitec DOT uni DASH bielefeld DOT de)]]) for an account and access to a project. Of course, the following descriptions are only valid for developers working at the Bielefeld Center for Biotechnology.

	== CVS Access ==		== CVS Access ==
Line 15:		Line 15:
	* gendb_web - for setting up the web interface		* gendb_web - for setting up the web interface
	* gendb_gui - for working on the Gtk GUI		* gendb_gui - for working on the Gtk GUI
	* !GOPArc - needed for the analysis of metabolic pathways and functional categories within !GenDB		* GOPArc - needed for the analysis of metabolic pathways and functional categories within GenDB
	* !SEED - needed for comparative analyses		* SEED - needed for comparative analyses

	== Setting up a GenDB Web-Server ==		== Setting up a GenDB Web-Server ==
Line 23:		Line 23:
	* edit `user_conf.sh`:		* edit `user_conf.sh`:
	** choose a free port number that is not already used by another developer, e.g. `PORT=9000`		** choose a free port number that is not already used by another developer, e.g. `PORT=9000`
	** set ~~CVS_!SUBDIR~~ relative to your !HOME directory, e.g. `CVS_SUBDIR=juser/cvs`		** set CVS_SUBDIR relative to your HOME directory, e.g. `CVS_SUBDIR=juser/cvs`
	* login to the test web server machine: e.g. `rsh hook`		* login to the test web server machine: e.g. `rsh hook`
	* `cd YOUR_INSTALL_DIR/gendb_web`		* `cd YOUR_INSTALL_DIR/gendb_web`
	* start the Apache web server: `./apache2 [configtest] start`		* start the Apache web server: `./apache2 [configtest] start`
	* point your favorite browser to the !GenDB start page: `hook:9000/software/gendb`		* point your favorite browser to the GenDB start page: `hook:9000/software/gendb`
	* you can find the error log on hook: 'tail -f ~~!YOUR_!INSTALL_DIR~~/gendb_web/share/logs/gendb2.error`		* you can find the error log on hook: 'tail -f YOUR_INSTALL_DIR/gendb_web/share/logs/gendb2.error`

	== Starting the GenDB Gtk GUI ==		== Starting the GenDB Gtk GUI ==