Go to file

Juan Antonio Osorio Robles f301600bee Fix leftover statement about the CA's CN

When the documentation pointed to using just a self-signed
certificate (with no CA), this was correct, however, as this changed,
this statement should have been updated as well, as it now gives
erronous advice about the CA's CN.

Change-Id: I09394a66c787ec1f4c8c0db75a70b5dfd868ef26

2016-11-15 10:10:23 +02:00

doc/source

Fix leftover statement about the CA's CN

2016-11-15 10:10:23 +02:00

.gitignore

Ignore both the AUTHORS and ChangeLog files

2016-03-18 09:40:52 +00:00

.gitreview

Add .gitreview

2015-09-09 10:09:29 +01:00

README.rst

Update README files for TripleO documentation

2016-01-14 16:10:32 +00:00

requirements.txt

Initial import of TripleO docs

2015-09-01 21:14:49 -04:00

setup.cfg

Merge "remove python 2.6 trove classifier"

2016-03-22 16:45:13 +00:00

setup.py

Initial import of TripleO docs

2015-09-01 21:14:49 -04:00

test-requirements.txt

Remove discover from test-requirements

2016-07-21 07:57:37 +00:00

tox.ini

Update the tox config to build the docs by default

2016-03-21 08:49:10 +00:00

README.rst

TripleO Documentation

This is the documentation source for the TripleO project. You can read the generated documentation at TripleO Docs.

You can find out more about TripleO at the TripleO Wiki.

Getting Started

Documentation for the TripleO project is hosted on the OpenStack Gerrit site. You can view all open and resolved issues in the openstack/tripleo-docs project at TripleO Reviews.

General information about contributing to the OpenStack documentation available at OpenStack Documentation Contributor Guide

Quick Start

The following is a quick set of instructions to get you up and running by building the TripleO documentation locally. The first step is to get your Python environment configured. Information on configuring is available at Python Project Guide

Next you can generate the documentation using the following command. Be sure to run all the commands from within the recently checked out repository.

tox -edocs

Now you have the documentation generated for the various available formats from the local source. The resulting documentation will be available within the doc/build/ directory.