c3e8fe6082
Replace the old http links with the lastest ones according to the OpenStack websites. Change-Id: I0adaabad70c67df885cccce744b4db447c8a0f75
52 lines
1.7 KiB
ReStructuredText
52 lines
1.7 KiB
ReStructuredText
========================
|
|
Team and repository tags
|
|
========================
|
|
|
|
.. image:: https://governance.openstack.org/tc/badges/tripleo-docs.svg
|
|
:target: https://governance.openstack.org/tc/reference/tags/index.html
|
|
|
|
.. Change things from this point on
|
|
|
|
TripleO Documentation
|
|
=====================
|
|
|
|
This is the documentation source for the TripleO project. You can read
|
|
the generated documentation at `TripleO
|
|
Docs <https://docs.openstack.org/tripleo-docs/latest/>`__.
|
|
|
|
You can find out more about TripleO at the `TripleO
|
|
Wiki <https://wiki.openstack.org/wiki/TripleO>`__.
|
|
|
|
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 <https://review.openstack.org/#/q/project:openstack/tripleo-docs>`__.
|
|
|
|
General information about contributing to the OpenStack documentation
|
|
available at `OpenStack Documentation Contributor
|
|
Guide <https://docs.openstack.org/doc-contrib-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 <https://docs.openstack.org/project-team-guide/project-setup/python.html>`__
|
|
|
|
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.
|