x/tuskar-ui
Code Issues Proposed changes

update quickstart doc to fix minor typos

Browse Source 
fixes bug 1002661
* Changes the name of the directory used for django to be
openstack_dashboard instead of openstack-dashboard
* updates the location of manage.py

Change-Id: I8f04fd90f59d85f0339bd59c9e8d478bcb84f9e2
This commit is contained in:
Tom Fifield 2012-05-22 16:46:15 +10:00
parent 4210177f93
commit 1a9a70ecae
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
AUTHORS
View File

@ -47,6 +47,7 @@ termie <github@anarkystic.com>
Thierry Carrez <thierry@openstack.org> Thierry Carrez <thierry@openstack.org>
Tihomir Trifonov <t.trifonov@gmail.com> Tihomir Trifonov <t.trifonov@gmail.com>
Todd Willey <todd@ansolabs.com> Todd Willey <todd@ansolabs.com>
Tom Fifield <fifieldt@unimelb.edu.au>
Tomasz 'Zen' Napierala <tomasz@napierala.org> Tomasz 'Zen' Napierala <tomasz@napierala.org>
Tres Henry <tres@treshenry.net> Tres Henry <tres@treshenry.net>
Vishvananda Ishaya <vishvananda@gmail.com> Vishvananda Ishaya <vishvananda@gmail.com>

15
docs/source/quickstart.rst
View File

@ -12,18 +12,17 @@ repository at http://github.com/openstack/horizon and execute the
Horizon assumes a single end-point for OpenStack services which defaults to Horizon assumes a single end-point for OpenStack services which defaults to
the local host (127.0.0.1). If this is not the case change the the local host (127.0.0.1). If this is not the case change the
``OPENSTACK_HOST`` setting in the ``local_settings.py`` file, located in the ``OPENSTACK_HOST`` setting in the ``local_settings.py`` file, located in the
``openstack-dashboard/local`` folder, to the actual IP address of the ``openstack_dashboard/local`` folder, to the actual IP address of the
OpenStack end-point Horizon should use. OpenStack end-point Horizon should use.
To start the Horizon development server use the Django ``manage.py`` utility To start the Horizon development server use the Django ``manage.py`` utility
from the ``openstack-dashboard`` directory with the context of the virtual with the context of the virtual environment::
environment::
> tools/with_venv.sh dashboard/manage.py runserver > tools/with_venv.sh ./manage.py runserver
Alternately specify the listen IP and port:: Alternately specify the listen IP and port::
> tools/with_venv.sh dashboard/manage.py runserver 0.0.0.0:8080 > tools/with_venv.sh ./manage.py runserver 0.0.0.0:8080
Once the Horizon server is running point a web browser to http://localhost:8000 Once the Horizon server is running point a web browser to http://localhost:8000
or to the IP and port the server is listening. or to the IP and port the server is listening.
@ -49,19 +48,19 @@ Horizon's Structure
This project is a bit different from other OpenStack projects in that it has This project is a bit different from other OpenStack projects in that it has
two very distinct components underneath it: ``horizon``, and two very distinct components underneath it: ``horizon``, and
``openstack-dashboard``. ``openstack_dashboard``.
The ``horizon`` directory holds the generic libraries and components that can The ``horizon`` directory holds the generic libraries and components that can
be used in any Django project. be used in any Django project.
The ``openstack-dashboard`` directory contains a reference Django project that The ``openstack_dashboard`` directory contains a reference Django project that
uses ``horizon``. uses ``horizon``.
For development, both pieces share an environment which (by default) is For development, both pieces share an environment which (by default) is
built with the ``tools/install_venv.py`` script. That script creates a built with the ``tools/install_venv.py`` script. That script creates a
virtualenv and installs all the necessary packages. virtualenv and installs all the necessary packages.
If dependencies are added to either ``horizon`` or ``openstack-dashboard``, If dependencies are added to either ``horizon`` or ``openstack_dashboard``,
they should be added to ``tools/pip-requires``. they should be added to ``tools/pip-requires``.
.. important:: .. important::