=== added directory 'doc'
=== added file 'doc/changes.rst'
--- doc/changes.rst	1970-01-01 00:00:00 +0000
+++ doc/changes.rst	2011-06-28 11:42:54 +0000
@@ -0,0 +1,9 @@
+Version History
+***************
+
+.. _version_0_5:
+
+Version 0.5
+===========
+
+* First documented version

=== added file 'doc/conf.py'
--- doc/conf.py	1970-01-01 00:00:00 +0000
+++ doc/conf.py	2011-06-28 11:42:54 +0000
@@ -0,0 +1,201 @@
+# -*- coding: utf-8 -*-
+#
+# LAVA Dashboard documentation build configuration file, created by
+# sphinx-quickstart on Mon Dec 27 16:39:47 2010.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys
+import os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+sys.path.append(os.path.abspath('..'))
+
+# -- General configuration -----------------------------------------------------
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.intersphinx', 'sphinx.ext.todo', 'sphinx.ext.coverage']
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = []
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General information about the project.
+project = u'Lava Dashboard'
+copyright = u'2010-2011, Linaro Limited'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+import versiontools
+import dashboard_app
+version = "%d.%d" % dashboard_app.__version__[0:2]
+# The full version, including alpha/beta/rc tags.
+release = versiontools.format_version(dashboard_app.__version__)
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#language = None
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
+
+# List of documents that shouldn't be included in the build.
+#unused_docs = []
+
+# List of directories, relative to source directory, that shouldn't be searched
+# for source files.
+exclude_trees = []
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  Major themes that come with
+# Sphinx are currently 'default' and 'sphinxdoc'.
+html_theme = 'default'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = []
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_use_modindex = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = ''
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'VersionToolsDocumentation'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+# The paper size ('letter' or 'a4').
+#latex_paper_size = 'letter'
+
+# The font size ('10pt', '11pt' or '12pt').
+#latex_font_size = '10pt'
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index', 'LavaDashboard.tex', u'Lava Dashboard Documentation',
+   u'Zygmunt Krynicki', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# Additional stuff for the LaTeX preamble.
+#latex_preamble = ''
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_use_modindex = True
+
+
+# Example configuration for intersphinx: refer to the Python standard library.
+intersphinx_mapping = {'http://docs.python.org/': None}

=== added file 'doc/index.rst'
--- doc/index.rst	1970-01-01 00:00:00 +0000
+++ doc/index.rst	2011-06-28 11:42:54 +0000
@@ -0,0 +1,29 @@
+============================
+Lava Dashboard Documentation
+============================
+
+.. automodule:: dashboard_app 
+
+.. seealso:: To get started quickly see :ref:`usage`
+.. seealso:: See what's new in :ref:`version_0_5`
+
+Features
+========
+
+
+
+Indices and tables
+==================
+
+.. toctree::
+    :maxdepth: 2
+    
+    installation.rst
+    usage.rst
+    changes.rst
+    reference.rst
+
+* :ref:`genindex`
+* :ref:`modindex`
+* :ref:`search`
+

=== added file 'doc/installation.rst'
--- doc/installation.rst	1970-01-01 00:00:00 +0000
+++ doc/installation.rst	2011-06-28 16:28:57 +0000
@@ -0,0 +1,347 @@
+Installation
+============
+
+This guide shows you how to setup a LAVA Dashboard instance running on Ubuntu
+Lucid Server (LTS). The installation was performed using Virtualbox
+4.0.10-72479~Ubuntu~natty running on a Ubuntu Natty Narwhal host.
+
+.. note::
+    Currently LAVA server-side installations support Ubuntu Lucid Lynx Server
+    *only*. Usually everything works on a more recent Ubuntu release, such as
+    Maverick Meerkat, Natty Narwhal and even Oneiric Ocelot however we cannot
+    guarantee that is the case. We welcome bug reports though, please let us
+    know.
+
+
+
+Getting Ubuntu Server
+^^^^^^^^^^^^^^^^^^^^^
+
+
+You can get Ubuntu Server from http://www.ubuntu.com/download/server/download
+Please ensure you get 10.04 LTS version. Feel free to use either 32bit or 64bit
+version, depending on your hardware needs.
+
+
+Installing Ubuntu Server
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+The installation is rather straightforward. For the purpose of this
+installation we selected ``English``
+
+.. image:: lava-dashboard-installation-0.png
+
+You need to make the same choice a moment later:
+
+.. image:: lava-dashboard-installation-1.png
+
+For country, territory or area we selected the default which is ``United
+States``. You can safely choose other values.
+
+.. image:: lava-dashboard-installation-2.png
+
+A few moments later the installer will allow you to configure networking. Here
+we selected `lava`. It does not matter much but if you have multiple Ubuntu
+installations it's a good idea to give each an unique host name.
+
+.. image:: lava-dashboard-installation-3.png
+
+A moment later you will have to create the initial user. This user will have
+administrative access to the system. For our demo we created an user called
+``Lava Admin``:
+
+.. image:: lava-dashboard-installation-4.png
+
+You also need to select a user name, we selected ``lava-admin``.
+
+.. image:: lava-dashboard-installation-5.png
+
+After that the installation is really up to you. You can partition the disk
+anyway you like. There is no need to select anything different from the
+defaults offered by the installer as far as LAVA is concerned.
+
+Once the installation is done login with the username and password you selected
+
+
+Adding the Lava Dashboard PPA
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+Currently LAVA is packaged in a PPA maintained by Zygmunt Krynicki. There is an
+official PPA being prepared (owned by the Linaro Validation group) but it is
+not ready as of 28th of June 2011.
+
+Usually PPAs are added using the very useful tool called
+``add-apt-repository``. It is not installed by default on server installations
+so we'll need to get it manually.  Let's install the package that has this tool
+``python-software-properties``,  using the following command::
+
+    $ sudo apt-get install python-software-properties
+
+You should see an output similar to the one below:
+
+.. image:: lava-dashboard-installation-6.png
+
+Now we can add the PPA using the following command::
+
+    $ sudo add-apt-repository ppa:zkrynicki/lava
+
+You should see an output similar to the one below:
+
+.. image:: lava-dashboard-installation-7.png
+
+After the PPA is added we need to update the cache of packages that APT knows about. This step is mandatory::
+
+    $ sudo apt-get update
+
+.. image:: lava-dashboard-installation-8.png
+
+This command does produce a lot of output. After it finishes we can finally install launch-control.
+
+
+Installing Lava Dashboard Package
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+To install the dashboard you need to install a package called
+``launch-control``.
+
+.. note::
+    Lava Dashboard used to be called Launch Control. The old name is being
+    transitioned but we have not prepared a packaged release of the new
+    codebase just yet.
+
+You can install this package using the following command::
+
+    $ sudo apt-get install launch-control
+
+.. image:: lava-dashboard-installation-9.png
+
+Running this command will make APT ask you for confirmation. It will display a
+list of packages that will be installed to fulfill the dependency chain of the
+dashboard. Here it required over 20 megabytes of additional packages.
+
+.. image:: lava-dashboard-installation-10.png
+
+Just confirm the selection and let it download all the packages.
+
+
+Setting Up The Dashboard Database
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+The installer will ask you several questions. Most of the questions come from a
+Debian subsystem used by the Dashboard to setup a database. This subsystem is
+called ``dbconfig-common``. The first question it asks if whether you wish you
+use dbconfig-common with launch-control.
+
+.. image:: lava-dashboard-installation-11.png
+
+Select ``<Yes>`` here please. If you select ``<No>`` instead you will have to
+manually create and configure a database. This is only recommended for advanced
+users and is not described in this guide.
+
+The next question is about the database back-end that the Dashboard should use
+to store test results and other data. The dashboard supports two back-ends:
+
+#. SQLite
+#. PostgreSQL
+
+.. image:: lava-dashboard-installation-12.png
+
+We recommend PostgreSQL for all installations. Some of the features, such as
+data mining and reporting, may have database-specific queries and those queries
+would not run on SQLite.
+
+.. note::
+    It is possible to provide custom data mining queries specific to a database
+    back-end so it's possible to have a query that would work on both SQLite
+    and PostgreSQL but the users are not required to provide such fall-backs.
+
+The final question is displayed only when using PostgreSQL.
+
+.. image:: lava-dashboard-installation-13.png
+
+Here ``dbconfig-common`` asks you about the password you would like to use for
+the database account that will be used by the dashboard to connect to
+PostgreSQL server. By default a random password will be generated for you, just
+leave this field blank and continue.
+
+After those questions the interactive part will finish and the dashboard will
+be installed and configured automatically. There is very little output, usually
+it looks like this:
+
+.. image:: lava-dashboard-installation-14.png
+
+There is much more details about what is happening but it is being redirected
+to ``syslog``. To have a look at that immediately after the installation you
+can use a command such as::
+
+    $ less /var/log/syslog
+
+Just scroll down to the end of the file (using page down key) to see the
+verbose installation details. If you have any questions about that please ask
+us.
+
+.. note::
+    Asking questions is good. It let's us know what we did wrong and let's us
+    build a FAQ for other users. You can find us in the #linaro channel on
+    irc.freenode.net. Usually we're up during EU and US timezones. You can also
+    use https://answers.launchpad.net/lava-dashboard
+
+
+Creating the admin user
+^^^^^^^^^^^^^^^^^^^^^^^
+
+The dashboard has a user account system separate from the system it is running
+on. To control it you need to have a administrator, super-user account. Create
+one now using this command::
+
+    $ sudo -u www-data /usr/lib/launch-control/manage.py createsuperuser
+
+.. image:: lava-dashboard-installation-15.png
+
+Answer the questions asked by the program. For the purpose of the guide we used
+``admin`` for both user name and password.
+
+.. image:: lava-dashboard-installation-16.png
+
+
+Powering off the virtual machine
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+We are almost ready to get started with the dashboard. Since we use VirtualBox
+and, by default, it is using NAT networking we are unable to connect to the
+dashboard from our host operating system. Let's turn off the virtual machine
+and reconfigure VirtualBox networking.
+
+To power off the virtual machine use the following command::
+
+    $ sudo poweroff
+
+.. image:: lava-dashboard-installation-17.png
+
+
+Reconfiguring virtual machine network
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+After the machine shuts down, go to the main VirtuaBox window (you may need to
+stat VirtualBox again if you closed it earlier). Next, click on the name of the
+virtual machine you created. This will change the pane on the right to display
+the configuration of your virtual machine. Locate network settings and click on
+the icon next to the label. This should bring up a dialog window similar to the
+one below.
+
+.. image:: lava-dashboard-installation-18.png
+
+As you can see the network adapter is attached to the ``NAT`` network. Let's
+change that to to ``Bridged Adapter``. If you have multiple network adapters
+available (such as wired networking and wireless networking) make sure to
+select the one you are connected with right now. We used ``wlan0`` which is the
+name of the wireless connection on the host computer.
+
+The settings should look like this:
+
+.. image:: lava-dashboard-installation-19.png
+
+Click okay to close the dialog window and start the machine again.
+
+
+Booting the virtual machine again
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+If you left the Ubuntu Lucid Server installation CD in the virtual machine as
+we did please select the option called ``Boot from first hard disk`` and continue.
+
+.. image:: lava-dashboard-installation-20.png
+
+After a moment the machine will be up and running. Let's log in to see the IP
+address it got from the DHCP server on your network.
+
+.. image:: lava-dashboard-installation-21.png
+
+Login with the user you created during operating system installation. As you
+remember we used the ``lava-admin`` user.
+
+.. image:: lava-dashboard-installation-22.png
+
+We now need to check the IP address of our virtual server. Use the following command now::
+
+    $ ifconfig
+
+.. image:: lava-dashboard-installation-23.png
+
+Here our IP address is ``10.155.3.51``, the value you'll see will most likely differ.
+
+
+Accessing the dashboard for the first time
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+Now we are ready to connect to the dashboard. From your host computer open a
+web browser of your choice (we used Firefox that came with Ubuntu Natty) and go
+to this address::
+
+    http://10.155.3.51/launch-control/
+
+Substitute the value above with the IP address of your server. You should see a screen like this:
+
+.. image:: lava-dashboard-installation-24.png
+
+Let's sign in with the admin user we created. Click on the sign in button in
+the top-right corner now.
+
+.. image:: lava-dashboard-installation-25.png
+
+.. note:: 
+    The dashboard supports two kinds of user accounts. You can create a local
+    account, like the one we did with ``createsuperuser`` or use an existing
+    launchpad.net account. For general use we recommend launchpad accounts as
+    that will not require creating yet-another password for you to remember.
+    This time, however, you need to sign in as the ``admin`` user with the
+    ``admin`` password we created earlier. This account is special and has
+    access to the administration panel, more such accounts can be created if
+    necessary.
+
+After signing in go click on the link that reads ``Bundle Stream``. It will
+lead you to a page that contains a list of all the streams in your dashboards.
+There are no streams yet so let's create one. Please follow the link on the
+page to go to the admin panel, directly to a place that allows you to create
+additional bundle streams.
+
+.. image:: lava-dashboard-installation-26.png
+
+.. note::
+    The dashboard uses the term ``stream`` but you can think of it as a
+    directory. It's just a directory in the system that can be used to store
+    test results in.
+
+You will see a form like the one on the screen shot below, make sure to select
+the ``admin`` from the ``Ownership`` section. This will make you the owner of
+the data stored in that stream. Also make sure to select the ``is public`` and
+``is anonymous`` check-boxes below in the ``Access Rights`` section. Finally
+click save.
+
+.. image:: lava-dashboard-installation-27.png
+
+.. note::
+    The dashboard has a simple ownership and access control system. It is not
+    described here but the settings you selected a moment ago will allow anyone
+    to upload and download test results to the bundle stream you just created.
+
+
+Now click on the address bar of your browser and go to this URL::
+
+    http://10.155.3.51/launch-control/dashboard/streams/
+
+As before, please replace the IP address with the IP address of your server.
+You should be able to see the ``/anonymous/`` bundle stream.
+
+.. image:: lava-dashboard-installation-28.png
+
+Congratulations, you have now correctly installed and configured the Lava
+Dashboard. You can now use lava-test and lava-dashboard-tool to upload data to
+your system.

=== added file 'doc/lava-dashboard-installation-0.png'
Binary files doc/lava-dashboard-installation-0.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-0.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-1.png'
Binary files doc/lava-dashboard-installation-1.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-1.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-10.png'
Binary files doc/lava-dashboard-installation-10.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-10.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-11.png'
Binary files doc/lava-dashboard-installation-11.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-11.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-12.png'
Binary files doc/lava-dashboard-installation-12.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-12.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-13.png'
Binary files doc/lava-dashboard-installation-13.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-13.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-14.png'
Binary files doc/lava-dashboard-installation-14.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-14.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-15.png'
Binary files doc/lava-dashboard-installation-15.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-15.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-16.png'
Binary files doc/lava-dashboard-installation-16.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-16.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-17.png'
Binary files doc/lava-dashboard-installation-17.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-17.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-18.png'
Binary files doc/lava-dashboard-installation-18.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-18.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-19.png'
Binary files doc/lava-dashboard-installation-19.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-19.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-2.png'
Binary files doc/lava-dashboard-installation-2.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-2.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-20.png'
Binary files doc/lava-dashboard-installation-20.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-20.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-21.png'
Binary files doc/lava-dashboard-installation-21.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-21.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-22.png'
Binary files doc/lava-dashboard-installation-22.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-22.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-23.png'
Binary files doc/lava-dashboard-installation-23.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-23.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-24.png'
Binary files doc/lava-dashboard-installation-24.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-24.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-25.png'
Binary files doc/lava-dashboard-installation-25.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-25.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-26.png'
Binary files doc/lava-dashboard-installation-26.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-26.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-27.png'
Binary files doc/lava-dashboard-installation-27.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-27.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-28.png'
Binary files doc/lava-dashboard-installation-28.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-28.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-3.png'
Binary files doc/lava-dashboard-installation-3.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-3.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-4.png'
Binary files doc/lava-dashboard-installation-4.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-4.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-5.png'
Binary files doc/lava-dashboard-installation-5.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-5.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-6.png'
Binary files doc/lava-dashboard-installation-6.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-6.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-7.png'
Binary files doc/lava-dashboard-installation-7.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-7.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-8.png'
Binary files doc/lava-dashboard-installation-8.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-8.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/lava-dashboard-installation-9.png'
Binary files doc/lava-dashboard-installation-9.png	1970-01-01 00:00:00 +0000 and doc/lava-dashboard-installation-9.png	2011-06-28 16:28:57 +0000 differ
=== added file 'doc/reference.rst'
--- doc/reference.rst	1970-01-01 00:00:00 +0000
+++ doc/reference.rst	2011-06-28 11:42:54 +0000
@@ -0,0 +1,6 @@
+.. _code_reference:
+
+Rereference
+^^^^^^^^^^^
+
+TODO

=== added file 'doc/usage.rst'
--- doc/usage.rst	1970-01-01 00:00:00 +0000
+++ doc/usage.rst	2011-06-28 11:42:54 +0000
@@ -0,0 +1,6 @@
+.. _usage:
+
+Usage
+*****
+
+TODO

=== added file 'setup.cfg'
--- setup.cfg	1970-01-01 00:00:00 +0000
+++ setup.cfg	2011-06-28 11:40:16 +0000
@@ -0,0 +1,5 @@
+[upload_docs]
+upload-dir=build/sphinx/html
+
+[upload]
+sign=True

