openstack
/
nova
Code Issues Proposed changes
nova/doc
History
James E. Blair 18a5ca1c20 Rename .nova-venv to .venv. 
This simplifies a number of Jenkins jobs which currently, other
than directory names, could be the same for all OpenStack
projects. By renaming the virtualenv directory, the redundant
Jenkins virtualenv build and copy jobs can be eliminated.

Cherry-picked from 5235106e95

Conflicts:

	.gitignore
	doc/source/devref/development.environment.rst

Change-Id: Ieaf1dac3207ecb34b911c7edcd2086809abdf49e
 		2011-12-13 07:48:23 -08:00
..
build generated files should not be in source control 2011-06-16 11:07:36 -05:00
ext execvp: fix docs 2011-03-09 17:22:54 -05:00
source Rename .nova-venv to .venv. 2011-12-13 07:48:23 -08:00
.gitignore Updated sphinx layout to a two-dir layout like swift. 2010-07-24 18:06:22 -07:00
Makefile Since we're autodocumenting from a sphinx ext, we can scrap it in Makefile. 2010-11-07 18:18:04 -05:00
README.rst Merge lp:~termie/nova/trunkdoc (via patch, since bzr though it was already merged) 2010-11-07 14:51:40 -05:00
find_autodoc_modules.sh quieter doc building (less warnings). 2010-11-07 14:58:02 -05:00
generate_autodoc_index.sh Cleanups to doc process. 2010-11-07 15:14:58 -05:00

README.rst

Building the docs

It is really easy. You'll need sphinx (the python one) and if you are using the virtualenv you'll need to install it in the virtualenv specifically so that it can load the nova modules.

Use make

Just type make:

% make

Look in the Makefile for more targets.

Manually

  1. Generate the code.rst file so that Sphinx will pull in our docstrings:

    % ./generate_autodoc_index.sh > source/code.rst

  2. Run `sphinx_build`:

    % sphinx-build -b html source build/html

The docs have been built

Check out the build directory to find them. Yay!