File	Date	Author	Commit
allura	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
docs	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
ez_setup	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
flyway	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
run	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
MANIFEST.in	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
README.txt	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
demo.ini	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
development.ini	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
oembed.ini	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
push_re.py	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
sandbox-test.ini	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
sandbox.ini	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
setup.cfg	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
setup.py	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...
test.ini	2010-08-13	Rick Copeland	[3abb2e] [#176] - s/pyforge(the egg)/Allura/g, s/pyforge...

Read Me

This file is for you to describe the allura application. Typically
you would include information such as the information below:

Installation and Setup
======================

Install ``allura`` using the setup.py script::

    $ cd allura
    $ python setup.py install

Create the project database for any model classes defined::

    $ paster setup-app development.ini

Start the paste http server::

    $ paster serve development.ini

While developing you may want the server to reload after changes in package files (or its dependencies) are saved. This can be achieved easily by adding the --reload option::

    $ paster serve --reload development.ini

Then you are ready to go.