openstack
/
horizon
Code Issues Proposed changes
OpenStack Dashboard (Horizon)
5,561 Commits 9 Branches 47 Tags 313 MiB
Python 63%
JavaScript 28.9%
HTML 6.5%
SCSS 1.5%
Go to file
lin-hua-cheng 5304e14559 Add max-complexity to pep8 for Horizon 
Picked this up from Keystone. It sounds like a good defense to have from
further making our code more complex.

The current highest complexity is 32, set the maximum complexity
for flake8 to 33. This should help to keep code simple and
maintainable. It should be possible to reduce the maximum
complexity to something closer to 20 with relatively small efforts.

openstack_dashboard.dashboards.identity.projects.workflows:
    'UpdateProject.handle' is complexity of 32
openstack_dashboard.dashboards.project.access_and_security.security_groups.forms:
    'AddRule.clean' is complexity of 20
openstack_dashboard.dashboards.project.instances.workflows.create_instance:
    'SetInstanceDetailsAction.clean' is complexity of 26
horizon.exceptions:
    'handle' is complexity of 24

Change-Id: I58cc20972aac221012f248e8135151b1243dae35
 		2014-10-18 18:57:43 -07:00
.tx Update .tx/config with type of files 2014-03-21 15:30:03 +01:00
doc Updates to horizon settings.rst 2014-10-13 19:05:56 +09:00
horizon Merge "Make labels in Network Topology translatable" 2014-10-18 14:15:51 +00:00
openstack_dashboard Merge "Update Horizon terminology relating to storage" 2014-10-18 20:05:50 +00:00
tools Remove requirements style check 2014-07-08 09:50:14 -07:00
.gitignore Remove compiled message catalogs 2014-10-10 05:31:32 +09:00
.gitreview Add .gitreview and rfc.sh. 2011-10-28 09:50:35 -04:00
.mailmap Update my mailmap 2013-10-25 14:49:23 +08:00
.pylintrc updating run_tests.sh to mimic other openstack projects, pep8, pylint, coverage 2011-08-31 14:41:36 -07:00
CONTRIBUTING.rst Add CONTRIBUTING.rst 2014-07-09 14:47:57 +08:00
HACKING.rst Remove #noqa from django.conf.urls.include 2014-09-29 13:58:39 +04:00
LICENSE Initial commit 2011-01-12 13:43:31 -08:00
MANIFEST.in Drop NodeJS dependency in favor of pure-python lesscpy 2013-08-16 09:31:08 +02:00
Makefile Unifies the project packaging into one set of modules. 2012-02-29 00:20:13 -08:00
README.rst Add install guide for users and clean up README 2014-10-09 03:29:26 +09:00
manage.py Gate on H102 Apache 2.0 license header not found for pep8 2013-11-19 13:55:04 -05:00
openstack-common.conf Remove unused openstack.common.importutils 2014-10-13 15:15:31 -07:00
requirements.txt Updated from global requirements 2014-10-13 18:45:33 +00:00
run_tests.sh Add check for makemessages in tox.ini PEP8 2014-10-10 05:38:53 +09:00
setup.cfg Open Kilo development 2014-09-30 16:56:21 +02:00
setup.py Updated from global requirements 2014-05-01 13:44:26 +00:00
test-requirements.txt Updated from global requirements 2014-10-11 22:31:54 +00:00
tox.ini Add max-complexity to pep8 for Horizon 2014-10-18 18:57:43 -07:00

README.rst

Horizon (OpenStack Dashboard)

Horizon is a Django-based project aimed at providing a complete OpenStack Dashboard along with an extensible framework for building new dashboards from reusable components. The openstack_dashboard module is a reference implementation of a Django site that uses the horizon app to provide web-based interactions with the various OpenStack projects.

Using Horizon

See doc/source/topics/install.rst about how to install Horizon in your OpenStack setup. It describes the example steps and has pointers for more detailed settings and configurations.

It is also available at http://docs.openstack.org/developer/horizon/topics/install.html.

Getting Started for Developers

doc/source/quickstart.rst or http://docs.openstack.org/developer/horizon/quickstart.html describes how to setup Horizon development environment and start development.

Building Contributor Documentation

This documentation is written by contributors, for contributors.

The source is maintained in the doc/source directory using reStructuredText and built by Sphinx

  • Building Automatically:

    $ ./run_tests.sh --docs

  • Building Manually:

    $ tools/with_venv.sh sphinx-build doc/source doc/build/html

Results are in the doc/build/html directory