semvec/pypi-packages huggingface dataset:
more.forwarded 0.2
Forwarded header support for Morepath
License: BSD
Keywords: morepath forwarded

more.forwarded: Forwarded header support for Morepath
=====================================================

If you want to run Morepath_ behind a trusted proxy that sets the
`Forwarded header`_, you can use ``more.forwarded`` to make Morepath
generate URLs that take this header into account.

**Note**: Only use this if you know you are behind a trusted proxy
that indeed sets the Forwarded header, otherwise you expose your
server to potential attacks.

.. _Morepath: http://morepath.readthedocs.org

.. _`Forwarded header`: http://tools.ietf.org/html/rfc7239

CHANGES
*******

0.2 (2016-04-26)
================

- Morepath 0.14 introduces a HOST_HEADER_PROTECTION tween that we
  should be used over. This stops the forwarded header from injecting
  incorrect Host headers.

- Make tests work with Morepath 0.14 and later.

0.1 (2014-11-25)
================

- Initial public release.
django-wms 0.1.12
Mapscript based WMS framework for GeoDjango
License: BSD
Keywords: django,gis,mapserver,mapscript,wms,tms,web map service,tile map service

Django WMS Framework
======================
The Django WMS Framework is a toolkit that makes it easy to build a `Web Map Service (WMS) <http://en.wikipedia.org/wiki/Web_Map_Service>`_ or a x-y-z `Tile Map Service <http://en.wikipedia.org/wiki/Tile_Map_Service>`_. Rendering of both vector and raster data formats are supported.

For complete documentation please go to `<http://django-wms.readthedocs.org>`_

Requirements
------------
The processing of spatial data in django-wms relies on `MapServer <http://mapserver.org/index.html>`_ and its python bindings `MapScript <http://mapserver.org/mapscript/mapscript.html>`_. Raster data integration depends on the `django-raster <https://pypi.python.org/pypi/django-raster/0.1.0>`_ package. The use of `PostGIS <http://postgis.net/>`_ as the database backend is required as well, for raster ntegration PostGIS >= 2.0 is required (see also django-raster package).

Installation
------------
1. Install package with ``pip install django-wms``

2. Add "wms" to your INSTALLED_APPS setting like this::

        INSTALLED_APPS = (
            ...
            'wms',
        )

Example
-------
To create a mapping service, subclass the django-wms layer, map and view classes and connect them to an existing model in django that has a spatial field (such as Point, Polygon or MultiPolygon). An example ``wms_config.py`` module could be specified as follows ::

    ### wms_config.py

    # Load django-wms classes
    from wms import maps, layers, views

    # Load model with spatial field (Point, Polygon or MultiPolygon)
    from myapp.models import MySpatialModel


    # Subclass the WmsVectorLayer class and point it to a spatial model.
    # Use WmsRasterLayer for rasters
    class MyWmsLayer(layers.WmsVectorLayer):
        model = MySpatialModel

    # Subclass the WmsMap class and add the layer to it
    class MyWmsMap(maps.WmsMap):
        layer_classes = [ MyWmsLayer ]

    # Subclass the WmsView to create a view for the map
    class MyWmsView(views.WmsView):
        map_class = MyWmsMap

With the WmsView subclass in place, the only thing left to do to create a functional map service is to hook the view into a url. An example url configuration ``urls.py`` could be ::

    ### urls.py

    # Import the wms view
    from myproject.wms_config import MyWmsView

    # Add url patterns to setup map services from the view
    urlpatterns = patterns('',

        # This creates a WMS endpoint
        url(r'^wms/$', MyWmsView.as_view(), name='wms'),

        # This creates a TMS endpoint
        url(r'^tile/(?P<layers>[^/]+)/(?P<z>[0-9]+)/(?P<x>[0-9]+)/(?P<y>[0-9]+)(?P<format>\.jpg|\.png)$',
            MyWmsView.as_view(), name='tms'),
    )

The django-wms package will automatically detect the first spatial field it can find in ``MySpatialModel`` and create a WMS endpoint from the class based view. If the three arguments ``x``, ``y`` and ``z`` are found in the urlpattern, the view functions as TMS endpoint.
eve-peewee 0.0.6
Data layer for Eve powered by peewee.
License: BSD

Eve Peewee extension
====================

`|Build Status| <https://travis-ci.org/stt/eve-peewee>`_

A WIP data layer for `Eve <http://python-eve.org/>`_ using
`peewee <http://peewee-orm.com/>`_

Currently peewee creates tables based on settings.py DOMAIN declarations
during start-up and basic Eve CRUD methods work.

Instuctions
^^^^^^^^^^^

-  ``python setup.py install`` or ``pip install eve-peewee``
-  define DATABASE\_URI in settings.py (see examples)
-  Eve(data=EvePeewee).run()

Tested
^^^^^^

-  postgres 9.x, sqlite3
-  python 2.7, 3.5
-  basic eve functionality (filtering, sorting, pagination, timestamps,
   etag/if-match, soft delete)
-  1:m data relationships

Untested/TBD
^^^^^^^^^^^^

-  mysql
-  custom validator
-  constraints (unique)
-  m:m data relationships (atm creates link tables but likely fails to
   query for embedding)
-  versioning fields

Notable caveats
^^^^^^^^^^^^^^^

-  peewee doesn't do auto-migration (if you change domain models, drop
   the tables to get them recreated or apply changes in db manually)
-  peewee specific field properties can be defined in DOMAIN schema
   (requires "transparent\_schema\_rules"), e.g.
   ``'_peewee': { 'primary_key': True }``
-  not all possible error cases are captured to json/xml document,
   default 500 response may happen
-  objectid and media types are unsupported (list and dict types are
   saved as jsonb)
-  many of the mongo centric field properties of eve (anyof, allof etc)
   are silently ignored

.. |Build Status| image:: https://travis-ci.org/stt/eve-peewee.svg