semvec/pypi-packages huggingface dataset:
sphinxjp.themes.dotted 0.1.2
A sphinx theme for Dotted style.
License: MIT
Keywords: sphinx,reStructuredText,theme

Dotted style theme for Sphinx.

Features
========
* provide ``dotted`` theme for render HTML document.


Set up
======
Make environment with pip::

    $ pip sphinxjp.themes.dotted


Convert Usage
=============
setup conf.py with::

    html_theme = 'dotted'

and run::

    $ make html


Requirement
===========
* Python 2.7 or later (not support 3.x)
* Sphinx 1.2.x or later.


License
=======
Licensed under the `MIT license <http://www.opensource.org/licenses/mit-license.php>`_ .
See the LICENSE file for specific terms.

AUTHORS
=======

Sphinx template, css, packaging
-------------------------------
* Shoji KUMAGAI <take.this.2.your.grave at gmail.com> sphinx-users.jp

History
=======

0.1.2 (Sep 09, 2014)
---------------------
* remove 'sphinxjp.themecore' dependency

0.1.1 (Nov 09, 2011)
---------------------
* add new functionalities

  * toggle to display sidebar or not
  * toggle to put sidebar on right side or not

0.1.0 (Oct 15, 2011)
---------------------
* first release
env-render 0.1.2
Generates files by parsing the environment with jinja2
License: MIT

env-render
==========

Render a file with jinja2 using a context built from processing environment
variables.

Installation
------------

From pip::
    
    $ pip install env-render

Usage
-----

To render a jinja document and collect all the environment variables with the
prefix `APP`, enter this command::
    
    $ env-render -p APP src_template.txt output.txt

Example
-------

So imagine this environment::
    
    APP_0_ENV0=a
    APP_0_ENV1=b
    APP_0_HOSTNAME=app_0
    APP_1_ENV0=c
    APP_1_ENV1=d
    APP_1_HOSTNAME=app_1
    APP_2_ENV0=e
    APP_2_ENV1=f
    APP_2_HOSTNAME=app_2

Becomes this dictionary::
    
    {
        "apps": [
            {
                "_index": 0,
                "ENV0": "a",
                "ENV1": "b",
                "HOSTNAME": "app_0"
            },
            {
                "_index": 1,
                "ENV0": "c",
                "ENV1": "d",
                "HOSTNAME": "app_1"
            },
            {
                "_index": 2,
                "ENV0": "e",
                "ENV1": "f",
                "HOSTNAME": "app_2"
            }
        ]
    }


Which can then be used like this in a file. Say an ``haproxy.cfg`` file::
    
    listen someapp
        bind 0.0.0.0:80

        {% for app in apps %}
        server server{{ app._index }} {{ app.HOSTNAME }}:80
        {% endfor %} 

This is what this library is meant to do.