semvec/pypi-packages huggingface dataset:
wagtail-constance 0.0.2
django-constance integration for Wagtail CMS
License: MIT
Keywords: django,config,constance

Wagtail-Constance
~~~~~~~~~~~~~~~~~

I know there is `wagtail.contrib.settings <http://docs.wagtail.io/en/latest/reference/contrib/settings.html>`_ available, but I'm a big fan of `django-constance <https://github.com/jazzband/django-constance>`_ with redis backend!



Installation
------------

Make sure you installed `django-constance <https://github.com/jazzband/django-constance>`_ then install wagtail-constance:

.. code-block:: sh
    
    pip install wagtail-constance


And then just add ``wagtailconstance`` into ``INSTALLED_APPS``:

.. code-block:: py

    INSTALLED_APPS = (
       ...
       'wagtailconstance',
       ...
    )

Note
----

I'm not added wagtail or constance as requirements in setup.py.
I'm tested it out only with python 3.5.1


Credits
-------

* Released under `MIT License <http://www.opensource.org/licenses/mit-license.php>`_
* `wagtail <https://github.com/torchbox/wagtail>`_
* `django-constance <https://github.com/jazzband/django-constance>`_
* this `snippet <https://djangosnippets.org/snippets/10462/>`_
scrapy-qiniu 0.1.2
Scrapy pipeline extension for qiniu.com
License: MIT
Keywords: crawler,spider,scrapy,qiniu

scrapy_qiniu
=====

Scrapy中的media pipeline机制，可以方便地将静态资源资源（文件、图像等）下载到本地，然后进行处理。scrapy-qiniu扩展了这一机制，可以将资源存储到七牛云存储上面。并且，实现了以下几个特性：

* 支持缓存，可以避免静态资源的重复下载
* 采用fetch模式，让七牛服务器代为下载，而不用像默认的FilesPipeline那样，先下载到爬虫所在
主机，然后再上传到七牛服务器
autodock-cron 0.0.2
autodock cron plugin
License: MIT
Keywords: autodock cron plugin docker

autodock-cron
=============

.. image:: https://badge.imagelayers.io/prologic/autodock-cron:latest.svg
   :target: https://imagelayers.io/?images=prologic/autodock-cron:latest
   :alt: Image Layers

Cron-like Plugin for autodock.

This plugin runs containers on a regular scheduled as defined by
the environment variable ``CRON`` of the form ``m h d mon dow``
much like crond on many Linux/UNIX systems.

The container must first be run at least once for ``autodock-cron``
to pick up the new container and its configuration.

Note that ``autodock-cron`` makes use of the Docker API and effectively
calls ``docker start`` on your container; a new container is **NOT** created
on very run of the schedule.

.. note:: See: `autodock <https://github.com/prologic/autodock>`_

Basic Usage
-----------

Start the daemon::
    
    $ docker run -d --name autodock prologic/autodock

Link and start an autodock plugin::
    
    $ docker run -d --link autodock prologic/autodock-cron

Run a container of your choice and set ``CRON=*/1 * * * *`` to run every minute::
    
    $ docker run --name hello -e CRON="*/1 * * * *" busybox sh -c 'echo Hello'

Now autodock-cron will schedule a timer to re-run this container every minute
until the container is deleted and removed. After about ~3mins you should get::
    
    $ docker logs hello
    Hello
    Hello
    Hello
autodock-hipache 0.0.2
autodock hipache plugin
License: MIT
Keywords: autodock hipache plugin docker

.. _a Docker-based mini-PaaS: http://shortcircuit.net.au/~prologic/blog/article/2015/03/24/a-docker-based-mini-paas/


autodock-hipache
================

.. image:: https://badge.imagelayers.io/prologic/autodock-hipache:latest.svg
   :target: https://imagelayers.io/?images=prologic/autodock-hipache:latest
   :alt: Image Layers

Hipache Plugin for autodock.

autodock-hipache is MIT licensed.

.. note:: See: `autodock <https://github.com/prologic/autodock>`_

Basic Usage
-----------

Start the daemon::
    
    $ docker run -d --name autodock prologic/autodock

Link and start the autodock Hipache Plugin::
    
    $ docker run -d --link autodock prologic/autodock-hipache

Now whenever you start a new container autodock will listen for Docker events
and discover containers that have been started. The ``autodock-hipache`` plugin
will specifically listen for starting containers that have a ``VIRTUALHOST``
environment variable and reconfigure the running ``hipache`` container.

An optional ``ALIAS`` environment value can be given as an extra virtualhost
typically used for a ``www.`` alias to a domain.

Start a "Hello World" Web Application::
    
    $ docker run -d -e VIRTUALHOST=hello.local prologic/hello
    curl -q -o - -H 'Host: hello.local' http://localhost/
    Hello World!

.. note:: This method of hosting and managing webapps and websites is in
          production deployments and talked about in more detail in the post
          `A Docker-based mini-PaaS`.

``docker-compose.yml``:

.. code:: yaml
    
   autodock:
       image: prologic/autodock
       volumes:
           - /var/run/docker.sock:/var/run/docker.sock

   autodockhipache:
       image: prologic/autodock-hipache
       links:
           - autodock
           - hipache:redis

   sslcerts:
       image: prologic/mksslcrt
       command: "*.mydomain.com"

   hipache:
       image: prologic/hipache
       ports:
           - "80:80"
           - "443:443"
       volumes_from:
           - sslcerts

   hello:
       image: prologic/hello
       environment:
           - VIRTUALHOST=hello.mydomain.com
           - ALIAS=hello.local

.. note:: The version of Hipache used here will not startup unless you have
          setup SSL certificates, so the sslcerts volume is requried for
          a correctly functionining system.
hipachectl 0.3.0
Command Line Tool to Manage hipache
License: MIT
Keywords: hipache manage docker

.. _docker: http://docker.com/
.. _dotCloud: http://dotcloud.com/
.. _hipache: https://github.com/hipache/hipache


hipachectl
==========

.. image:: https://badge.imagelayers.io/prologic/hipachectl:latest.svg
   :target: https://imagelayers.io/?images=prologic/hipachectl:latest
   :alt: Image Layers

hipachectl is a command-line tool and library to manage `dotCloud`_'s
`hipache`_ load balancer and reverse proxy. hipachectl lets you:

- list configured virtual hosts
- add a new virtual host
- delete a virtual host

hipachectl is MIT licensed.

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

Either pull the automatically updated `Docker`_ image::
    
    $ docker pull prologic/hipachectl

Or install from the development repository::
    
    $ git clone https://github.com/prologic/hipachectl.git
    $ cd hipachectl
    $ pip install .

 
Usage
-----

To use hipachectl from `Docker`_::
    
    $ docker run prologic/hipachectl -u tcp://ip:port <command>

Or::
    
    $ hipachectl -u tcp://ip:port <command>

Where ``ip`` and ``port`` are the IP Address and Port of the `hipache`_
instance or the IP/Port of the Redis instance used. e.g: ``tcp://redis:6379``

Or if you have a named `hipache`_ instance you can use ``--link``::
    
    $ docker run --link hipache prologic/hipachectl

For help use the ``--help`` option.

Change Log
==========

0.2 (2015-05-26)
----------------

-  Moved project to `Github <https://github.com/prologic/hipachectl>`_

0.1 (2015-05-26)
----------------

-  Added an API

0.0.1 (2014-11-01)
------------------

-  Initial Release
autodock-logger 0.0.2
autodock logger plugin
License: MIT
Keywords: autodock logger plugin docker

autodock-logger
===============

Logger plugin for autodock.

autodock-logger is MIT licensed.

.. note:: See: `autodock <https://github.com/prologic/autodock>`_


Basic Usage
-----------


Start the daemon::
    
    $ docker run -d -v /var/run/docker.sock:/var/run/docker.sock --name autodock prologic/autodock

Link and start an autodock plugin::
    
    $ docker run -i -t --link autodock prologic/autodock-logger

Now whenever you start a new container autodock will listen for Docker events.
The ``autodock-logger`` plugin will log all Docker Events received by autodock.

``docker-compose.yml``:

.. code:: yaml
    
    autodock:
        image: prologic/autodock
        ports:
            - "1338:1338/udp"
            - "1338:1338/tcp"
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock

    autodocklogger:
        image: prologic/autodock-logger
        links:
            - autodock