openwisp-utils

---

Python and Django utilities shared between different OpenWISP modules.

---

Table of Contents:

• Current features
• Project goals
• Install stable version from pypi
• Install development version
• Using the utilities in OpenWISP modules
  • Using the admin_theme
  • Admin mixins
  • Using DependencyLoader and DependencyFinder
    • DependencyFinder
    • DependencyLoader
  • Quality Assurance checks
    • checkmigrations
    • checkcommit
• Installing for development
• Contributing
• Changelog
• License
• Support

---

Current features

• Customized admin theme for OpenWISP modules
• TimeStamped models and mixins which add self-updating created and modified fields.
• UUIDModel: base model with a UUID4 primary key
• DependencyLoader: template loader which looks in the templates dir of all django-apps listed in EXTENDED_APPS
• DependencyFinder: finds static files of django-apps listed in EXTENDED_APPS
• QA: logic and utilities to perform quality assurance checks across different modules

Project goals

• Minimize code duplication among OpenWISP modules

Install stable version from pypi

Install from pypi:

pip install openwisp-utils
# install optional dependencies for tests (flake8 and isort)
pip install openwisp-utils[qa]

Install development version

Install tarball:

pip install https://github.com/openwisp/openwisp-utils/tarball/master

Alternatively you can install via pip using git:

pip install -e git+git://github.com/openwisp/openwisp-utils#egg=openwisp-utils

If you want to contribute, install your cloned fork:

git clone git@github.com:<your_fork>/openwisp-utils.git
cd openwisp-utils
python setup.py develop

Using the utilities in OpenWISP modules

INSTALLED_APPS in settings.py should look like the following if you want to use the OpenWISP admin-theme:

INSTALLED_APPS = [
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    # customized admin theme
    'openwisp_utils.admin_theme',
    # all-auth
    'django.contrib.sites',
    'allauth',
    'allauth.account',
    'allauth.socialaccount',
    'django_extensions',
    # openwisp2 modules
    'openwisp_users',
    # admin
    'django.contrib.admin',
]

Using the admin_theme

For using the customized admin theme,

• Make sure you've added openwisp_utils.admin_theme to INSTALLED_APPS in settings.py
• Add the following into your urls.py file which contains admin urls.

from django.conf.urls import include, url

from openwisp_utils.admin_theme.admin import admin, openwisp_admin

openwisp_admin()

urlpatterns = [
    # other url patterns
    url(r'^admin/', include(admin.site.urls)),
]

Admin mixins

• TimeReadonlyAdminMixin: Admin mixin which adds two readonly fields created and modified. This is an admin mixin for models inheriting TimeStampedEditableModel which adds the fields created and modified to the database.

Using DependencyLoader and DependencyFinder

Add the list of all packages extended to EXTENDED_APPS in settings.py. If you've extended django_netjsonconfig and django_x509:

EXTENDED_APPS = ['django_netjsonconfig', 'django_x509']

DependencyFinder

Add openwisp_utils.staticfiles.DependencyFinder to STATICFILES_FINDERS in settings.py.

STATICFILES_FINDERS = [
    'django.contrib.staticfiles.finders.FileSystemFinder',
    'django.contrib.staticfiles.finders.AppDirectoriesFinder',
    'openwisp_utils.staticfiles.DependencyFinder',
]

DependencyLoader

Add openwisp_utils.staticfiles.DependencyFinder to TEMPLATES_LOADERS in settings.py or as shown below.

TEMPLATES = [
    {
        'BACKEND': 'django.template.backends.django.DjangoTemplates',
        'DIRS': [],
        'OPTIONS': {
            'loaders': [
                'django.template.loaders.filesystem.Loader',
                'django.template.loaders.app_directories.Loader',
                'openwisp_utils.loaders.DependencyLoader',
            ],
            'context_processors': [
                'django.template.context_processors.debug',
                'django.template.context_processors.request',
                'django.contrib.auth.context_processors.auth',
                'django.contrib.messages.context_processors.messages',
            ],
        },
    },
]

Quality Assurance checks

This package contains some common QA checks that are used the automated builds of different OpenWISP modules.

checkmigrations

Ensures the latest migrations created have a human readable name.

We want to avoid having many migrations named like 0003_auto_20150410_3242.py.

This way we can reconstruct the evolution of our database schemas faster, with less efforts and hence less costs.

Usage example:

checkmigrations --migration-path ./django_freeradius/migrations/

checkcommit

Ensures the last commit message follows our commit message style guidelines.

We want to keep the commit log readable, consistent and easy to scan in order to make it easy to analyze the history of our modules, which is also a very important activity when performing maintenance.

Usage example:

checkcommit --message "$(git log --format=%B -n 1)"

Installing for development

Install sqlite:

sudo apt-get install sqlite3 libsqlite3-dev

Install your forked repo:

git clone git://github.com/<your_fork>/openwisp-utils
cd openwisp-utils/
python setup.py develop

Install test requirements:

pip install -r requirements-test.txt

Create database:

cd tests/
./manage.py migrate
./manage.py createsuperuser

You can access the admin interface of the test project at http://127.0.0.1:8000/admin/.

Run tests with:

./runtests.py

Contributing

1. Announce your intentions in the OpenWISP Mailing List and open relavant issues using the issue tracker
2. Fork this repo and install the project following the instructions
3. Follow PEP8, Style Guide for Python Code
4. Write code and corresponding tests
5. Ensure that all tests pass and the test coverage does not decrease
6. Document your changes
7. Send a pull request

Changelog

See CHANGES.

License

See LICENSE.

Support

See OpenWISP Support Channels.