Tree [3e805d] 42cc /
History



File Date Author Commit
Allura 2012-03-22 Yaroslav Luzin Yaroslav Luzin [3e805d] Merge branch 'master' into 42cc
AlluraTesting 2011-11-23 Dave Brondsema Dave Brondsema [d80b08] [#3324] force params to be strings in functiona...
ForgeBlog 2012-03-30 Yaroslav Luzin Yaroslav Luzin [9a71ee] Merge branch 'dev'
ForgeChat 2011-11-22 Tim Van Steenburgh Tim Van Steenburgh [9f4059] [#2931] Allow changing mount labels.
ForgeDiscussion 2012-03-16 Yaroslav Luzin Yaroslav Luzin [b5a45d] Merge branch 'master' into 42cc
ForgeDownloads 2012-01-20 Jenny Steele Jenny Steele [fb496c] [#3556] External link and Download tools now us...
ForgeGit 2012-02-03 Rick Copeland Rick Copeland [5cb772] [#2709] Fix error found by dave
ForgeHg 2012-02-03 Rick Copeland Rick Copeland [5cb772] [#2709] Fix error found by dave
ForgeLink 2012-01-20 Jenny Steele Jenny Steele [fb496c] [#3556] External link and Download tools now us...
ForgeSVN 2012-02-08 Dave Brondsema Dave Brondsema [0aaca3] [#2709] test the refresh_commit fix
ForgeTracker 2012-03-21 Yaroslav Luzin Yaroslav Luzin [7aebf7] Merge branch 'master' into 42cc
ForgeWiki 2012-03-19 Yaroslav Luzin Yaroslav Luzin [af22da] Merge branch 'master' into 42cc
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-03-16 Yaroslav Luzin Yaroslav Luzin [b5a45d] Merge branch 'master' into 42cc
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-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-03-12 Yaroslav Luzin Yaroslav Luzin [91bb85] Merge branch 'dev' of ssh://git.code.sf.net/p/a...
Makefile.def.buildbot 2012-03-12 Yaroslav Luzin Yaroslav Luzin [91bb85] Merge branch 'dev' of ssh://git.code.sf.net/p/a...
README.markdown 2012-03-30 Yaroslav Luzin Yaroslav Luzin [9a71ee] Merge branch 'dev'
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 2012-03-26 Yaroslav Luzin Yaroslav Luzin [7dc2cc] Merge branch 'master' into t13_projectlist
requirements-dev.txt 2012-03-26 Yaroslav Luzin Yaroslav Luzin [7dc2cc] Merge branch 'master' into t13_projectlist
requirements.txt 2012-03-21 Yaroslav Luzin Yaroslav Luzin [7aebf7] Merge branch 'master' into 42cc
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 11.10 to create a disposable sandbox for Forge development/testing.

  • Download and install VirtualBox for your platform.

  • Download a minimal Ubuntu 11.10 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 libtidy-0.99-0

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-jdk python-dev libssl-dev libldap2-dev libsasl2-dev libjpeg8-dev zlib1g-dev
~$ sudo ln -s /usr/lib/x86_64-linux-gnu/libz.so /usr/lib

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 aptitude install mongodb-server 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 aptitude install python-setuptools
~$ sudo easy_install -U 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. 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://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!