semvec/pypi-packages huggingface dataset:
emencia-recipe-drdump 0.3.1
Buildout recipe for 'Dr Dump'
License: MIT

.. _Django: https://www.djangoproject.com
.. _Dr Dump: https://github.com/emencia/dr-dump
.. _Buildout: http://www.buildout.org

`Buildout`_ recipe for `Dr Dump`_ to generate bash script to dump or load `Django`_ data dump.

So this recipe will create two bash scripts, one to dump datas from defined eggs in buildout config and another to load these dumped datas.

This will use the defined eggs list in your buildout config to find the apps to manage dumps so be careful that it can't retrieve apps that are not defined in your eggs to install, it will not follow eggs dependancies but if needed you can *force* some apps using the ``extra_apps`` option.

recipe
    Required, fill it with ``emencia-recipe-drdump``.
eggs
    Optional, 'eggs' variable from buildout. Default use ``${buildout:eggs}``.
dump_dir
    Optional, a path to the directory that will contains dumped datas, this is always a relative path from the buildout project. If not defined the dumps dir will be ``dumps``.
dependancies_map
    Required, a path to a JSON file containing datas dependancies map between apps. This can be either a file name existing in Dr Dump or a path (relative or absolute) to an external JSON file.
extra_apps
    Optional, a string of app names formatted like the egg names in ``${buildout:eggs}``. This will be used to defined additional apps that can't be retrieved from the installed eggs.
django_instance
    Required, a path to the django script, usually the one generated by *djangorecipe*.
silent
    Optional, false or true to define respectively if Dr Dump raise or not an exception when asked dumps does not exists in the used map.
dump_other_apps
    Optional, false or true to define if Dr Dump will dump not specify apps in a last dump.
exclude_apps
    Optional, a string of app names formatted like the egg names in ``${buildout:eggs}``. This will be used to defined additional apps that can't be dump if ``dump_other_apps`` is True.
bin_directory
    Optional, binary directory path where the scripts will be written, defaut use ``${buildout:bin-directory}``.

Here is a sample to use this recipe : ::

    [drdump]
    recipe                  = emencia-recipe-drdump
    dump_dir                = dumps
    dependancies_map        = djangocms-3.json
    silent                  = true
    dump_other_apps         = true
    exclude_apps            = auth sessions contenttypes menus.cachekey filebrowser
    django_instance         = ${buildout:directory}/bin/django-instance
    extra_apps              = cmsplugin-various
    bin_directory           = ${buildout:bin-directory}
vhostino 0.0.1
Virtual Hosts Plugin for Mozilla Circus
License: MIT

About VHostino
-------------------------

vhostino is a virtual hosts manager for `Mozilla Circus <https://github.com/mozilla-services/circus>`_.

Installing
-------------------------------

vhostino can be installed from pypi::

    easy_install vhostino

or::

    pip install vhostino

should just work for most of the users

Using VHostino
---------------------------------

Simply **name your watcher and socket as the domain** they have to serve and set
``vhostino.vhost = True`` to make them serve through virtual hosts on the vhostino ``port``::

    [plugin:vhostino]
    use = vhostino.VHostino
    host = 0.0.0.0
    port = 8000

    [watcher:www.mywebsite.com]
    cmd = chaussette --fd $(circus.sockets.www.mywebsite.com) myapp.application
    use_sockets = True

    vhostino.vhost = True

    uid = www-data
    gid = www-data

    [socket:www.mywebsite.com]
    host = 127.0.0.1
    port = 8082


The ``myapp.application`` web application will be served as usual on ``127.0.0.1:8082``
but will be also available on port ``8000`` when the domain ``www.mywebsite.com`` is requested.

Default Virtual Host
---------------------------

By default VHostino will answer with a 404 error whenever a non configured host is requested,
to serve a default virtual host simply set the ``vhostino.default_vhost = True`` option inside
a watcher, whenever a virtual host is not available to serve the request it will be proxied to
that process.

Notes
---------------------------

To perform virtual hosts resolution vhostino uses the ``watcher`` name, so make sure that
your watchers are named like the domain they need to serve. In future versions aliases
will also be added.

To match ``socket`` and ``watcher`` vhostino uses their name, so make sure that your socket
share the same name, otherwise vhostino won't be able to detect the process port.