Tree [53028a] master allura_20110825.01 /
History



File Date Author Commit
Allura 2011-08-25 Tim Van Steenburgh Tim Van Steenburgh [53028a] [#2380] Fix test.
AlluraTesting 2011-06-09 Dave Brondsema Dave Brondsema [1e5bee] [#2269] fix typo; make pyflakes errors less ver...
ForgeBlog 2011-08-25 Tim Van Steenburgh Tim Van Steenburgh [22db6e] Merge branch 'dev' of git://sfi-engr-scm-1/forg...
ForgeChat 2011-05-16 Rick Copeland Rick Copeland [dcb73d] [#2020] Update Allura to use the new Ming decla...
ForgeDiscussion 2011-08-09 Wayne Witzel III Wayne Witzel III [8eb330] Merge branch 'tv/2544' into dev
ForgeDownloads 2011-06-08 Jenny Steele Jenny Steele [917c50] [#2254] Going to the downloads tool mount point...
ForgeGit 2011-08-18 Tim Van Steenburgh Tim Van Steenburgh [098fd3] [#2380] Fix SCM fork tracking.
ForgeHg 2011-08-18 Tim Van Steenburgh Tim Van Steenburgh [098fd3] [#2380] Fix SCM fork tracking.
ForgeLink 2011-06-24 Jenny Steele Jenny Steele [3f2897] [#2117] Removed flyway migrations and organized...
ForgeSVN 2011-05-16 Rick Copeland Rick Copeland [dcb73d] [#2020] Update Allura to use the new Ming decla...
ForgeTracker 2011-08-19 Jenny Steele Jenny Steele [850408] [#2636] Long urls in ticket names will now wrap...
ForgeWiki 2011-08-18 Jenny Steele Jenny Steele [9b6a93] [#2614] Fixed wiki redirects to 404 correctly w...
NoWarnings 2011-02-01 Wolf Wolf [23c644] License is Apache 2
fuse 2011-01-31 Rick Copeland Rick Copeland [4a1607] [#1206] Fixes based on review feedback
scripts 2011-07-19 Jenny Steele Jenny Steele [e290c5] [#2372] Added neighborhood_blog_posts macro
solr_config 2010-03-23 Rick Copeland Rick Copeland [01d9bf] [#118] - Testing infrastructure upgrades
.gitattributes 2011-03-13 Wolf Wolf [4f057b] make git-diff hunk headers python-aware
.gitignore 2011-06-10 John Hoffmann John Hoffmann [ea1c27] Adding the teamforge export dir to .gitignore
.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
README.markdown 2011-04-15 Dave Brondsema Dave Brondsema [8abfc6] bump solr version number in README
coverage-report-all.sh 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 2011-08-16 John Hoffmann John Hoffmann [b2e53a] [#2533] Add additional GA custom variables
requirements-dev.txt 2011-06-08 John Hoffmann John Hoffmann [9411c8] [#2262] Move our Pygments req into req.txt and ...
requirements.txt 2011-07-07 Wayne Witzel III Wayne Witzel III [f6593a] [#2467] changed requirements, added import guar...
run_tests 2011-04-28 Dave Brondsema Dave Brondsema [f6375a] remove unused solr bootstrap from run_tests
schema.xml 2010-02-12 Jenny Steele Jenny Steele [69d856] 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. Note that RabbitMQ is optional, but will make messages flow faster through our asynchronous processors. By default, rabbitmq is disabled in development.ini.

~$ 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

If you want to use RabbitMQ for faster message processing (optional), also pip install 'amqplib' and 'kombu'.

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
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.1/apache-solr-1.4.1.tgz
(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 &

RabbitMQ message queue (optional)

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 task processing

Responds to asynchronous task requests.

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

And now you should be able to visit the server running on your local machine.
You can log in with username admin1, test-user or root. They all have password "foo". (For more details
on the default data, see bootstrap.py)

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!