Skip to main content

Use Django's template engine to render static files at deployment time. Extend Django's url reverse mechanism to JavaScript.

Project description

MIT license PyPI version fury.io PyPI pyversions PyPI status Documentation Status Code Cov Test Status

django-render-static

Use Django’s dynamic templates to render static files. That is, files that are collected during the collectstatic routine and likely served above Django on the stack. Static templates should be rendered preceding any run of collectstatic.

For example, a frequently occurring pattern that violates the DRY principle is the presence of defines, or enum like structures in server side Python code that are simply replicated in client side JavaScript. Single-sourcing these structures by generating client side code from the server side code maintains DRYness.

Have you ever wished you could replicate Django’s reverse function in a JavaScript library for your site? Now you can with the urls_to_js template tag included with django-render-static.

You can report bugs and discuss features on the issues page.

Contributions are encouraged! Especially additional template tags and filters!

Full documentation at read the docs.

Installation

  1. Clone django-render-static from GitHub or install a release off PyPI :

pip install django-render-static
  1. Add ‘render_static’ to your INSTALLED_APPS :

INSTALLED_APPS = [
    'render_static',
]
  1. Add a STATIC_TEMPLATES configuration directive to your settings file:

STATIC_TEMPLATES = {
    'templates' : {
        'path/to/template': {
            'context' { 'variable': 'value' }
        }
}
  1. Run render_static preceding every run of collectstatic :

$> manage.py render_static
$> manage.py collectstatic

Usage

Generating Javascript Defines

You have an app with a model with a character field that has several valid choices defined in an enumeration type way, and you’d like to export those defines to JavaScript. You’d like to include a template for other’s using your app to use to generate a defines.js file. Say your app structure looks like this:

.
└── my_app
    ├── __init__.py
    ├── apps.py
    ├── defines.py
    ├── models.py
    ├── static_templates
    │   └── my_app
    │       └── defines.js
    └── urls.py

Your defines/model classes might look like this:

class Defines:

    DEFINE1 = 'D1'
    DEFINE2 = 'D2'
    DEFINE3 = 'D3'
    DEFINES = (
        (DEFINE1, 'Define 1'),
        (DEFINE2, 'Define 2'),
        (DEFINE3, 'Define 3')
    )

class MyModel(Defines, models.Model):

    define_field = models.CharField(choices=Defines.DEFINES, max_length=2)

And your defines.js template might look like this:

var defines = {
    {{ "my_app.defines.Defines"|split|classes_to_js }}
};

If someone wanted to use your defines template to generate a JavaScript version of your Python class their settings file might look like this:

STATIC_TEMPLATES = {
    'templates': {
        'my_app/defines.js': {}
    }
}

And then of course they would call render_static before collectstatic:

$> ./manage.py render_static
$> ./manage.py collectstatic

This would create the following file:

.
└── my_app
    └── static
        └── my_app
            └── defines.js

Which would look like this:

var defines = {
    Defines: {
        DEFINE1: 'D1'
        DEFINE2: 'D2'
        DEFINE3: 'D3'
        DEFINES: [
            ['D1', 'Define 1'],
            ['D2', 'Define 2'],
            ['D3', 'Define 3']
        ]
    }
};

URL reverse functions

You’d like to be able to call something like reverse on path names from your client JavaScript code the same way you do from Python Django code. You don’t want to expose your admin paths though.

Your settings file might look like:

from pathlib import Path

BASE_DIR = Path(__file__).parent

STATICFILES_DIRS = [
    BASE_DIR / 'more_static'
]

STATIC_TEMPLATES = {
    'ENGINES': [{
        'BACKEND': 'render_static.backends.StaticDjangoTemplates',
        'OPTIONS': {
            'loaders': [
                ('render_static.loaders.StaticLocMemLoader', {
                    'urls.js': (
                        'var urls = {\n
                            {% urls_to_js exclude=exclude %}
                        \n};'
                    )
                })
             ],
            'builtins': ['render_static.templatetags.render_static']
        },
    },
    'templates': {
        'urls.js': {
            'dest': BASE_DIR / 'more_static' / 'urls.js',
            'context': {
                'exclude': ['admin']
            }
        }
    }]

Then call render_static before collectstatic:

$> ./manage.py render_static
$> ./manage.py collectstatic

If your root urls.py looks like this:

from django.contrib import admin
from django.urls import include, path

from .views import MyView

urlpatterns = [
    path('admin/', admin.site.urls),
    path('simple', MyView.as_view(), name='simple'),
    path('simple/<int:arg1>', MyView.as_view(), name='simple'),
    path('different/<int:arg1>/<str:arg2>', MyView.as_view(), name='different'),
]

Then urls.js will look like this:

var urls = {
    "simple": function(kwargs={}, args=[]) {
        if (Object.keys(kwargs).length === 0 && args.length === 0)
            return "/simple";
        if (
            Object.keys(kwargs).length === 1 &&
            ['arg1'].every(value => kwargs.hasOwnProperty(value))
        )
            return `/simple/${kwargs["arg1"]}`;
        throw new TypeError("No reversal available for parameters at path: simple");
    },
    "different": function(kwargs={}, args=[]) {
        if (
            Object.keys(kwargs).length === 2 &&
            ['arg1','arg2'].every(value => kwargs.hasOwnProperty(value))
        )
            return `/different/${kwargs["arg1"]}/${kwargs["arg2"]}`;
        throw new TypeError("No reversal available for parameters at path: different");
    }
}

So you can now fetch paths like this:

// /different/143/emma
urls.different({'arg1': 143, 'arg2': 'emma'});

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-render-static-0.1.1.tar.gz (23.7 kB view details)

Uploaded Source

Built Distribution

django_render_static-0.1.1-py3-none-any.whl (24.6 kB view details)

Uploaded Python 3

File details

Details for the file django-render-static-0.1.1.tar.gz.

File metadata

  • Download URL: django-render-static-0.1.1.tar.gz
  • Upload date:
  • Size: 23.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.4 CPython/3.6.10 Darwin/19.6.0

File hashes

Hashes for django-render-static-0.1.1.tar.gz
Algorithm Hash digest
SHA256 a31a6adede5b4b27ce8d4b20a19dd0f71edabd0aefda8e955d8283b64417b95c
MD5 0be916f8f962d5e896e9baf14fba35e5
BLAKE2b-256 f88660fa5b7b4703a1e0612370db79cf3485e7584807b0a6dafd95c4957653c3

See more details on using hashes here.

File details

Details for the file django_render_static-0.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for django_render_static-0.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 6939e6868722a0d8606a7fe830c7d2571c4f82c3ff1bf2daaba6951d23c7e1e0
MD5 3240fe811fbe9786d92cd0705d7a4d59
BLAKE2b-256 25ff46e71b06f64f8fc454627a585bad5fef2ae05741e6712eeb454a499fd7d5

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page