Tree [efd00b] 42cc_4524 /

File Date Author Commit
Allura 2012-05-24 Igor Bondarenko Igor Bondarenko [efd00b] [#4187] ticket:69 expand test and fix functiona...
AlluraTesting 2012-04-25 Dave Brondsema Dave Brondsema [bce604] [#4103] Mock SMTP during all functional tests
ForgeBlog 2012-05-25 bolkimen bolkimen [5deded] [#4254] ticket:64 fix command test error
ForgeChat 2012-04-25 Dave Brondsema Dave Brondsema [bce604] [#4103] Mock SMTP during all functional tests
ForgeDiscussion 2012-05-09 Rick Copeland Rick Copeland [e6846e] [#3940] Make forum markdown description display...
ForgeDownloads 2012-04-25 Dave Brondsema Dave Brondsema [bce604] [#4103] Mock SMTP during all functional tests
ForgeGit 2012-05-16 Cory Johns Cory Johns [081972] [#4116] DIVs inside PREs are a no-no
ForgeHg 2012-05-16 Cory Johns Cory Johns [081972] [#4116] DIVs inside PREs are a no-no
ForgeLink 2012-04-25 Dave Brondsema Dave Brondsema [bce604] [#4103] Mock SMTP during all functional tests
ForgeSVN 2012-05-18 Jenny Steele Jenny Steele [5a6594] [#4015] Fixes for svn commits missing data brea...
ForgeTracker 2012-05-15 bolkimen bolkimen [b99417] [#3019] ticket:53 replace patience with difflib
ForgeWiki 2012-05-15 bolkimen bolkimen [b99417] [#3019] ticket:53 replace patience with difflib
NoWarnings 2011-02-01 Wolf Wolf [23c644] License is Apache 2
fuse 2011-11-19 Rick Copeland Rick Copeland [943e3a] Fix FUSE filesystem to handle path correctly
scripts 2012-05-14 Cory Johns Cory Johns [1c05df] [#4118] Added chunking, intermediate flushing, ...
solr_config 2010-03-23 Rick Copeland Rick Copeland [01d9bf] [#118] - Testing infrastructure upgrades
vagrant 2012-04-24 Dave Brondsema Dave Brondsema [9af2cf] [#3907] improve process grepping, and little mo...
.gitattributes 2011-03-13 Wolf Wolf [4f057b] make git-diff hunk headers python-aware
.gitignore 2011-11-01 Dave Brondsema Dave Brondsema [da0d23] Merge branch 'master' into dev
.gitmodules 2009-12-01 Wolf Wolf [e4830b] Remove Ming submodule
CONTRIBUTING 2011-02-08 Wolf Wolf [7bca86] point CONTRIBUTING at the public support bug tr...
LICENSE 2011-02-01 Wolf Wolf [23c644] License is Apache 2
Makefile 2012-02-10 Yaroslav Luzin Yaroslav Luzin [c49955] ticket:2 Added a simple Makefile required for g...
Makefile.def.buildbot 2012-02-24 Yaroslav Luzin Yaroslav Luzin [6a2bc2] ticket:2 Upgraded fix for pysvn
README.markdown 2012-04-30 Dave Brondsema Dave Brondsema [3b4e13] [#4140] update README scm dir to match dev.ini'... 2011-01-27 Paul Sokolovsky Paul Sokolovsky [397c72] [#1237] Add script to produce combined coverage...
rebuild.bash 2011-03-30 Paul Sokolovsky Paul Sokolovsky [76fa99] Remove reference to no longer existing pyforge ...
requirements-common.txt 2012-05-21 Tim Van Steenburgh Tim Van Steenburgh [c3736d] Bump TimerMiddleware version.
requirements-sf.txt 2012-05-16 Dave Brondsema Dave Brondsema [e51bd5] [#4181] remove html2text from requirements-sf.t...
requirements.txt 2012-03-28 Dave Brondsema Dave Brondsema [268dc0] rename requirements-dev.txt->requirements.txt
run_tests 2011-04-28 Dave Brondsema Dave Brondsema [f6375a] remove unused solr bootstrap from run_tests

Read Me

Sandbox Creation

We'll use VirtualBox and Ubuntu 12.04 (11.10 works too) to create a disposable sandbox for Forge development/testing.

  • Download and install VirtualBox for your platform.

  • Download a minimal Ubuntu 12.04 64-bit ISO.

  • 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.

  • After a text-only installation, you may end up with a blank screen and blinking cursor. Press Alt-F1 to switch to the first console.

  • 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 aptitude install git-core subversion python-svn

You'll also need additional development packages in order to compile some of the modules. Use google for additional PIL/jpeg help.

~$ sudo aptitude install default-jre-headless python-dev libssl-dev libldap2-dev libsasl2-dev libjpeg8-dev zlib1g-dev
~$ sudo ln -s /usr/lib/x86_64-linux-gnu/ /usr/lib
~$ sudo ln -s /usr/lib/x86_64-linux-gnu/ /usr/lib

And finally our document-oriented database, MongoDB

~$ sudo aptitude install mongodb-server

If you are using a different base system, make sure you have Mongo 1.8 or better. If you need to upgrade, you can download the latest from

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 aptitude install python-pip
~$ sudo pip install virtualenv

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

~$ virtualenv --system-site-packages anvil

This gives us a nice, clean environment into which we can install all the forge dependencies. (The site-packages flag is to include the python-svn package). 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

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:// forge

Although the application 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$ pip install -r requirements.txt

This will take a while. If you get an error from pip, it is typically a temporary download error. Just run the command again and it will quickly pass through the packages it already downloaded and then continue.

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
    pushd $APP
    python develop

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
    mkdir -p ~/var/scm/$SCM
    chmod 777 ~/var/scm/$SCM
    sudo ln -s ~/var/scm/$SCM /tmp

Initializing the environment

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

SOLR search and indexing server

We have a custom config ready for use.

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

Forge task processing

Responds to asynchronous task requests.

(anvil)~$ cd ~/src/forge/Allura
(anvil)~/src/forge/Allura$ nohup paster taskd development.ini > ~/logs/taskd.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 taskd 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 &

Next Steps

Go to the server running on your local machine port 8080.
You can log in with username admin1, test-user or root. They all have password "foo". (For more details
on the default data, see

There are a few default projects (like "test") and neighborhoods. Feel free to experiment with them. If you want to
register a new project in your own forge, visit /p/add_project