git clone https://@opensourceprojects.eu/git/p/osp/osp-allura osp-osp-allura



File Date Author Commit
Allura 2011-03-17 Rick Copeland Rick Copeland [6899de] [#1723] Begin work on events to replace @react,...
AlluraTesting 2011-03-15 Rick Copeland Rick Copeland <Commit 22d026e23861bb450fef9bb4aa6e5ddbd286c28a> [#232] More test fixes
ForgeBlog 2011-03-14 Rick Copeland Rick Copeland <Commit 875040f83c58cbcee7a46e769fd4d5d698eed89d> [#1564] Use pyramid-like engine:package:path no...
ForgeChat 2011-02-14 Dave Brondsema Dave Brondsema <Commit 2a755ce5d5a6dba465e7f55962b08c89159d4828> [#1116] tidy up command usage
ForgeDiscussion 2011-03-23 Rick Copeland Rick Copeland <Commit 8b0acbfea7e320945423dafd6a5a25e21fbf092a> [#1763] Provide guard against 500 error seen in...
ForgeDownloads 2011-03-14 Rick Copeland Rick Copeland <Commit 875040f83c58cbcee7a46e769fd4d5d698eed89d> [#1564] Use pyramid-like engine:package:path no...
ForgeGit 2011-03-15 Rick Copeland Rick Copeland <Commit e1b8d54991b9f3f9e53540c50cf02355998006ea> [#1723] Replace amqp audit/react stuff with bac...
ForgeHg 2011-03-15 Rick Copeland Rick Copeland <Commit e1b8d54991b9f3f9e53540c50cf02355998006ea> [#1723] Replace amqp audit/react stuff with bac...
ForgeLink 2011-03-14 Rick Copeland Rick Copeland <Commit 875040f83c58cbcee7a46e769fd4d5d698eed89d> [#1564] Use pyramid-like engine:package:path no...
ForgeMail 2011-03-18 Dave Brondsema Dave Brondsema <Commit 15ed62288dac8b9d8812237678e61fb45a54966c> [#1676] after trying iso-8559-1 try utf-8
ForgeSVN 2011-03-15 Rick Copeland Rick Copeland <Commit e1b8d54991b9f3f9e53540c50cf02355998006ea> [#1723] Replace amqp audit/react stuff with bac...
ForgeTracker 2011-03-16 Wolf Wolf <Commit 9052295e8b0a58292428a777adf5b93a7d67928e> Fix validation errors that are making Hudson un...
ForgeWiki 2011-03-14 Rick Copeland Rick Copeland <Commit 875040f83c58cbcee7a46e769fd4d5d698eed89d> [#1564] Use pyramid-like engine:package:path no...
NoWarnings 2011-02-01 Wolf Wolf <Commit 23c644ff05fdc87e89b443afe1f6f9d25b4e2cff> License is Apache 2
fuse 2011-01-31 Rick Copeland Rick Copeland <Commit 4a160787d47fc9afcc0f05262ae81c0d18a76836> [#1206] Fixes based on review feedback
scripts 2011-03-14 Paul Sokolovsky Paul Sokolovsky <Commit 48bfd0648cc6120073fabb34087efa7563d2a7e3> [#1618] Move 3rd-party migration scripts to scr...
solr_config 2010-03-23 Rick Copeland Rick Copeland <Commit 01d9bfb1ddef49835820f1d10b2414ba56703480> [#118] - Testing infrastructure upgrades
.gitattributes 2011-03-13 Wolf Wolf <Commit 4f057bfbac58f84bffea3fdfa9e562415a6bf359> make git-diff hunk headers python-aware
.gitignore 2011-01-27 Paul Sokolovsky Paul Sokolovsky <Commit 504029120943dae5adca986a6459f908b56b46a1> [#1237] Make running coverage tests easier - su...
.gitmodules 2009-12-01 Wolf Wolf <Commit e4830bd691eb52e6ae1e0921b09247bf4ec3aed5> Remove Ming submodule
CONTRIBUTING 2011-02-08 Wolf Wolf <Commit 7bca86bf47f006c317d0b7cfd10bee12903e4bba> point CONTRIBUTING at the public support bug tr...
LICENSE 2011-02-01 Wolf Wolf <Commit 23c644ff05fdc87e89b443afe1f6f9d25b4e2cff> License is Apache 2
README.markdown 2011-03-14 John Hoffmann John Hoffmann <Commit 7f7c83ec97639255744b772e64a1486c59e58416> [#1542] Update the feedparser version number an...
coverage-report-all.sh 2011-01-27 Paul Sokolovsky Paul Sokolovsky <Commit 397c7248c20c9f4d79ed28b0c480ba1e0a891bf2> [#1237] Add script to produce combined coverage...
rebuild.bash 2011-01-11 Wolf Wolf <Commit 9151c98effe5512d3fb70815046145f0480125a8> Merge branch 'master' into dev
requirements-common.txt 2011-03-18 Dave Brondsema Dave Brondsema <Commit 67275d9656cd86c868229afbcb2d611434eefee0> [#1542] re-remove deps that were removed in 268...
requirements-dev.txt 2011-03-18 John Hoffmann John Hoffmann <Commit 25699f0ff6deb5a068dee997e175021eba517ba9> [#1542] This is in common now, no need to insta...
requirements.txt 2011-03-14 John Hoffmann John Hoffmann <Commit 7f7c83ec97639255744b772e64a1486c59e58416> [#1542] Update the feedparser version number an...
run_tests 2011-03-15 Rick Copeland Rick Copeland <Commit 2ef7af9e78eadd2971cbd11fc991ac48266677fc> [#1564] Update ForgeChat for new expose syntax
schema.xml 2010-02-12 Jenny Steele Jenny Steele <Commit 69d85666fc5c4464ad7a1731231e414fdfc5a965> Merge branch 'master' of ssh://engr.geek.net/forge

Read Me

Sandbox Creation

We'll use VirtualBox and Ubuntu 10.10 to create a disposable sandbox for Forge development/testing.

  • Download and install VirtualBox for your platform.

  • Download a minimal Ubuntu 10.10 ISO (~15MB).

  • Create a new virtual machine in Virtual Box, selecting Ubuntu (64 bit) as the OS type. The rest of the wizards' defaults are fine.

  • When you launch the virtual machine for the first time, you will be prompted to attach your installation media. Browse to the mini.iso that you downloaded earlier.

  • Consult available documentation for help installing Ubuntu.

Forge Installation

Before we begin, you'll need the following additional packages in order to work with the Forge source code.

~$ sudo apt-get install git-core gitweb subversion python-svn libtidy-0.99-0

You'll also need additional development packages in order to compile some of the modules.

~$ sudo apt-get install default-jdk python-dev libssl-dev libldap2-dev libsasl2-dev

And finally our document-oriented database, MongoDB, and our messaging server, RabbitMQ.

~$ sudo apt-get install mongodb rabbitmq-server

Setting up a virtual python environment

The first step to installing the Forge platform is installing a virtual environment via virtualenv. This helps keep our distribution python installation clean.

~$ sudo apt-get install python-setuptools
~$ sudo easy_install-2.6 -U virtualenv

Once you have virtualenv installed, you need to create a virtual environment. We'll call our Forge environment 'anvil'.

~$ virtualenv anvil

This gives us a nice, clean environment into which we can install all the forge dependencies. In order to use the virtual environment, you'll need to activate it. You'll need to do this whenever you're working on the Forge codebase so you may want to consider adding it to your ~/.bashrc file.

~$ . anvil/bin/activate

Now that that's out of the way, we'll go ahead and install TurboGears.

(anvil)~$ easy_install pylons==0.9.7
(anvil)~$ easy_install -i http://www.turbogears.org/2.1/downloads/2.1b2/index/ tg.devtools==2.1b2 TurboGears2==2.1b2

Installing the Forge code and dependencies

Now we can get down to actually getting the Forge code and dependencies downloaded and ready to go.

(anvil)~$ mkdir src
(anvil)~$ cd src
(anvil)~/src$ git clone git://git.code.sf.net/p/allura/git.git forge

Although the application setup.py files define a number of dependencies, the requirements.txt files are currently the authoritative source, so we'll use those with pip to make sure the correct versions are installed.

(anvil)~/src$ cd forge
(anvil)~/src/forge$ easy_install pip
(anvil)~/src/forge$ pip install -r requirements-dev.txt

And now to setup each of the Forge applications for development. Because there are quite a few (at last count 15), we'll use a simple shell loop to set them up.

for APP in Allura* Forge* NoWarnings pyforge
do
    pushd $APP
    python setup.py develop
    popd
done

Hopefully everything completed without errors. We'll also need to create a place for Forge to store any SCM repositories that a project might create.

for SCM in git svn hg
do
    mkdir -p ~/var/scm/$SCM
    chmod 777 ~/var/scm/$SCM
    sudo ln -s ~/var/scm/$SCM /
done

Initializing the environment

The forge consists of several components, all of which need to be running to have full functionality.

MongoDB database server

Generally set up with its own directory, we'll use ~/var/mongodata to keep our installation localized. We also need to disable the default distribution server.

(anvil)~$ sudo service mongodb stop
(anvil)~$ sudo update-rc.d mongodb remove

(anvil)~$ mkdir -p ~/var/mongodata ~/logs
(anvil)~$ nohup mongod --dbpath ~/var/mongodata > ~/logs/mongodb.log &

SOLR search and indexing server

We have a custom config ready for use.

(anvil)~$ cd ~/src
(anvil)~/src$ wget http://apache.mirrors.tds.net/lucene/solr/1.4.0/apache-solr-1.4.0.tgz
(anvil)~/src$ tar xf apache-solr-1.4.0.tgz
(anvil)~/src$ cd apache-solr-1.4.0/example/
(anvil)~/src/apache-solr-1.4.0/example/$ mkdir -p ~/src/forge/solr_config/conf
(anvil)~/src/apache-solr-1.4.0/example/$ cp solr/conf/solrconfig.xml ~/src/forge/solr_config/conf/
(anvil)~/src/apache-solr-1.4.0/example/$ nohup java -Dsolr.solr.home=$(cd;pwd)/src/forge/solr_config -jar start.jar > ~/logs/solr.log &

RabbitMQ message queue

We'll need to setup some development users and privileges.

(anvil)~$ sudo rabbitmqctl add_user testuser testpw
(anvil)~$ sudo rabbitmqctl add_vhost testvhost
(anvil)~$ sudo rabbitmqctl set_permissions -p testvhost testuser ""  ".*" ".*"

Forge "reactor" processing

Responds to RabbitMQ messages. We'll need to perform some setup operations before we can start it.

(anvil)~$ cd ~/src/forge/Allura
(anvil)~/src/forge/Allura$ paster reactor_setup development.ini
(anvil)~/src/forge/Allura$ nohup paster reactor development.ini > ~/logs/reactor.log &

Forge SMTP for inbound mail

Routes messages from email addresses to tools in the forge.

(anvil)~/src/forge/Allura$ nohup paster smtp_server development.ini > ~/logs/smtp.log &

TurboGears application server

In order to initialize the Forge database, you'll need to run the following:

(anvil)~/src/forge/Allura$ paster setup-app development.ini

This shouldn't take too long, but it will start the reactor server doing tons of stuff in the background. It should complete in 5-6 minutes. Once this is done, you can start the application server.

(anvil)~/src/forge/Allura$ nohup paster serve --reload development.ini > ~/logs/tg.log &

And now you should be able to visit the server running on your local machine.
You can log in with username test-admin, test-user or root. They all have password "foo".

Next Steps

Generate the documentation

Forge documentation currently lives in the Allura/docs directory and can be converted to HTML using Sphinx:

(anvil)~$ cd ~/src/forge/Allura/docs
(anvil)~/src/forge/Allura/docs$ easy_install sphinx
(anvil)~/src/forge/Allura/docs$ make html

You will also want to give the test suite a run, to verify there were no problems with the installation.

(anvil)~$ cd ~/src/forge
(anvil)~/src/forge$ export ALLURA_VALIDATION=none
(anvil)~/src/forge$ ./run_tests

Happy hacking!