Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Tree [665780] master /
History



File Date Author Commit
Allura 2013-08-14 Dave Brondsema Dave Brondsema [665780] [#6553] fix tests corresponding to taskd error ...
AlluraTest 2013-07-26 Yuriy Arhipov Yuriy Arhipov [e23020] [#3154] ticket:407 ForgeBlog API refactoring
ForgeActivity 2013-04-18 Peter Hartmann Peter Hartmann [6f8012] Override newline after license header in jinja2...
ForgeBlog 2013-07-29 Yuriy Arhipov Yuriy Arhipov [93d12e] [#3154] ticket:407 added pagination and locati...
ForgeChat 2013-07-18 Tim Van Steenburgh Tim Van Steenburgh [2dcec8] [#5517] Add permission descriptions
ForgeDiscussion 2013-07-24 Anton Kasyanov Anton Kasyanov [8b994e] [#6446] ticket:400 removed threads from forum json
ForgeGit 2013-08-13 Cory Johns Cory Johns [dfafc6] [#5177] Added test for default source and targe...
ForgeImporters 2013-08-08 Dave Brondsema Dave Brondsema [3cd016] [#6458] standardize importer label
ForgeLink 2013-07-18 Tim Van Steenburgh Tim Van Steenburgh [2dcec8] [#5517] Add permission descriptions
ForgeSVN 2013-07-18 Tim Van Steenburgh Tim Van Steenburgh [2dcec8] [#5517] Add permission descriptions
ForgeShortUrl 2013-07-18 Tim Van Steenburgh Tim Van Steenburgh [2dcec8] [#5517] Add permission descriptions
ForgeTracker 2013-08-02 Tim Van Steenburgh Tim Van Steenburgh [512ee4] [#6480] Add trac ticket importer plugin
ForgeUserStats 2013-07-18 Tim Van Steenburgh Tim Van Steenburgh [2dcec8] [#5517] Add permission descriptions
ForgeWiki 2013-08-08 Tim Van Steenburgh Tim Van Steenburgh [ee1c59] [#6458] Refactored Google Code project extractor
NoWarnings 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary
fuse 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary
scripts 2013-08-02 Tim Van Steenburgh Tim Van Steenburgh [512ee4] [#6480] Add trac ticket importer plugin
solr_config 2013-03-12 Igor Bondarenko Igor Bondarenko [5b2dfd] [#2835] ticket:290 Make solr's `text` field stored
vagrant 2013-05-25 Dave Brondsema Dave Brondsema [846381] [#6255] remove symlink workarounds for PIL
.gitattributes 2011-03-13 Wolf Wolf [4f057b] make git-diff hunk headers python-aware
.gitignore 2013-07-23 Cory Johns Cory Johns [227396] [#6456] Added documentation for ForgeImporters ...
.gitmodules 2009-12-01 Wolf Wolf [e4830b] Remove Ming submodule
.travis.yml 2013-06-03 Cory Johns Cory Johns [cf25d5] [#6287] Remove symlink workarounds for PIL from...
CONTRIBUTING 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary
LICENSE 2011-02-01 Wolf Wolf [23c644] License is Apache 2
Makefile 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary
Makefile.def.buildbot 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary
NOTICE 2013-04-18 Peter Hartmann Peter Hartmann [ee4602] [#4648] Add NOTICE file in top directory
README.markdown 2013-06-17 Tim Van Steenburgh Tim Van Steenburgh [2761f3] [#4559] In README, %s/anvil/env-allura/g
coverage-report-all.sh 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary
rat-excludes.txt 2013-05-06 Dave Brondsema Dave Brondsema [37e91c] [#4122] rename AlluraTesting dir to AlluraTest,...
rebuild-all.bash 2013-04-15 Peter Hartmann Peter Hartmann [c17704] [#4648] Add missing license headers
requirements-common.txt 2013-08-06 Dave Brondsema Dave Brondsema [fb0626] [#6461] remove gdata dep since it'll be replace...
requirements-optional.txt 2013-07-31 Tim Van Steenburgh Tim Van Steenburgh [868694] Move requests pkg to common dependencies
requirements-sf.txt 2013-08-13 Dave Brondsema Dave Brondsema [fea4b5] [#6458] add GoogleCodeWikiImporter to requireme...
requirements.txt 2013-04-24 Cory Johns Cory Johns [022d84] [#6093] Moved WebError requirement so it's not ...
run_clonedigger 2013-05-06 Dave Brondsema Dave Brondsema [37e91c] [#4122] rename AlluraTesting dir to AlluraTest,...
run_tests 2013-05-28 Dave Brondsema Dave Brondsema [d2a60b] [#6277] make forgeuserstats tmp repos not confl...
update.sh 2013-04-12 Peter Hartmann Peter Hartmann [ddf08c] Apply Apache License 2.0 header where necessary

Read Me

Sandbox Creation

We'll use VirtualBox and Ubuntu 12.04 (11.10 works too) to create a disposable sandbox for Allura 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.

Installation

Before we begin, you'll need to install some system packages.

~$ sudo aptitude install git-core default-jre-headless python-dev libssl-dev libldap2-dev libsasl2-dev libjpeg8-dev zlib1g-dev

To install MongoDB 2.2.3, follow the instructions here:

http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/

Optional, for SVN support:

~$ sudo aptitude install subversion python-svn

Setting up a virtual python environment

The first step to installing the Allura 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 Allura environment 'env-allura'.

~$ virtualenv env-allura

This gives us a nice, clean environment into which we can install all the allura dependencies.
In order to use the virtual environment, you'll need to activate it:

~$ . env-allura/bin/activate

You'll need to do this whenever you're working on the Allura codebase so you may want to consider adding it to your ~/.bashrc file.

Installing the Allura code and dependencies

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

(env-allura)~$ mkdir src
(env-allura)~$ cd src
(env-allura)~/src$ git clone https://git-wip-us.apache.org/repos/asf/incubator-allura.git allura

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.

(env-allura)~/src$ cd allura
(env-allura)~/src/allura$ 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.

Optional, for SVN support: symlink the system pysvn package into our virtual environment

(env-allura)~/src/allura$ ln -s /usr/lib/python2.7/dist-packages/pysvn ~/env-allura/lib/python2.7/site-packages/

And now to setup the Allura applications for development. If you want to setup all of them, run ./rebuild-all.bash
If you only want to use a few tools, run:

cd Allura
python setup.py develop
cd ../ForgeWiki   # required tool
python setup.py develop
# repeat for any other tools you want to use

Initializing the environment

The Allura 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.

(env-allura)~$ cd ~/src
(env-allura)~/src$ wget -nv http://archive.apache.org/dist/lucene/solr/4.2.1/solr-4.2.1.tgz
(env-allura)~/src$ tar xf solr-4.2.1.tgz && rm -f solr-4.2.1.tgz
(env-allura)~/src$ cp -f allura/solr_config/schema.xml solr-4.2.1/example/solr/collection1/conf

(env-allura)~/src$ cd solr-4.2.1/example/
(env-allura)~/src/apache-solr-1.4.1/example/$ mkdir ~/logs/
(env-allura)~/src/apache-solr-1.4.1/example/$ nohup java -jar start.jar > ~/logs/solr.log &

Allura task processing

Allura uses a background task service called "taskd" to do async tasks like sending emails, and indexing data into solr, etc. Let's get it running

(env-allura)~$ cd ~/src/allura/Allura
(env-allura)~/src/allura/Allura$ nohup paster taskd development.ini > ~/logs/taskd.log &

The application server

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

(env-allura)~/src/allura/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. Once this is done, you can start the application server:

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

Next Steps

Go to the Allura webapp running on your local machine port 8080.
(If you're running this inside a VM, you'll probably have to configure the port forwarding settings)

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)

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

Extra