semvec/pypi-packages huggingface dataset:
ddcheck 0.0.1
Check URLs and manage the respective records in DynDNS.
License: BSD

=======
ddcheck
=======

Check URLs and manage the respective records in DynDNS.


Description
===========

``ddcheck`` accepts a list of healthckeck URLs, resolve them to IPs and makes
HTTP requests directly to the IPs. When given IP is recognized as down, it will
remove the record from DynDNS

Features
--------

* IPv4 and IPv6 support (A and AAAA records in DNS)
* Traversing over CNAMEs to target A/AAAA records
* IP is marked as failed when it either timeouts (configurable in seconds) or
  returns defined HTTP code (for example 500, by default turned off)
* Dry run mode: Will not change the DynDNS recods. Outputs only ``curl`` commands
  instead.
* Will not delete IPs from DynDNS, when all the IPs in the dns record fail.

Installation
============

``pip install 'git+https://github.com/whiskybar/ddcheck.git#egg=ddcheck'``


Usage
=====


CLI
---

DynDNS credetials can be defined either by env variables, or as parameters.

::

    # ddcheck --help

    usage: ddcheck [-h] [-d] [-e ERROR_CODES] [-t TIMEOUT] [-D]
                   [--dynect-customer DYNECT_CUSTOMER] [--dynect-user DYNECT_USER]
                   [--dynect-password DYNECT_PASSWORD]
                   URL [URL ...]

    Run a ddcheck.

    positional arguments:
      URL                   URL to check

    optional arguments:
      -h, --help            show this help message and exit
      -d, --debug           Debug logging on
      -e ERROR_CODES, --error-codes ERROR_CODES
                            HTTP codes considered as non-OK
      -t TIMEOUT, --timeout TIMEOUT
                            URL timeout
      -D, --dry-run         Do not really update the dyndns. Just print records to
                            delete.
      --dynect-customer DYNECT_CUSTOMER
                            Customer name in DynEct (defaults to
                            DYNECT_CUSTOMER_NAME env variable)
      --dynect-user DYNECT_USER
                            Username in DynEct (defaults to DYNECT_USER_NAME env
                            variable)
      --dynect-password DYNECT_PASSWORD
                            Password in DynEct (defaults to DYNECT_PASSWORD env
                            variable)



Example
~~~~~~~

::

    export DYNECT_PASSWORD=aaa
    export DYNECT_USER_NAME=bbb
    export DYNECT_CUSTOMER_NAME=ccc
    ddcheck -e 500 --debug --dry-run http://root.example1.com/health/ http://cname.example2.com/check/

Python
------

Example
~~~~~~~
django-orgco 0.1.0
django-orgco implements a template tag to use orgco easily in django templates
License: BSD

django-orgco
============

.. image:: https://travis-ci.org/paetzke/django-orgco.png?branch=master
  :target: https://travis-ci.org/paetzke/django-orgco
.. image:: https://coveralls.io/repos/paetzke/django-orgco/badge.png?branch=master
  :target: https://coveralls.io/r/paetzke/django-orgco?branch=master

Copyright (c) 2013, Friedrich Paetzke (f.paetzke@gmail.com)
All rights reserved.

django-orgco implements a template tag to use orgco easily in django templates.

How to use
----------

Install the package via ``pip``

.. code:: bash

    $ pip install django-orgco

Add the package to your installed apps in settings.py.

.. code:: python

    INSTALLED_APPS = (
        ...
        'django_orgco',
        ...
    )

Then use it. Here is an example:

my_template.html:

.. code:: html

    {% load orgdoc %}
    
    {% orgdoc %}
    * header is here
    
    - short1 :: long1
    - short2 :: long2
    - short3 :: long3
    
    | th1 | th2 |
    |-----+-----|
    | td1 | td2 |
    {% endorgdoc %}

To enable code highlighting add *highlight* to *orgdoc*:

.. code:: html

    {% orgdoc highlight %}
    is_ok = True
    {% endorgdoc %}

The tag does not produce safe output by default. You have to mark it as safe yourself:

.. code:: html

    {% load orgdoc %}
    {% orgdoc highlight %}
    {{ code|safe }}
    {% endorgdoc %}

.. image:: https://d2weczhvl823v0.cloudfront.net/paetzke/django-orgco/trend.png
  :target: https://bitdeli.com/free
python-livefyre 0.1.3
API wrapper for Livefyre v3
License: BSD
Keywords: python-livefyre

===============================
Python Livefyre
===============================

.. image:: https://badge.fury.io/py/python-livefyre.png
    :target: http://badge.fury.io/py/python-livefyre

.. image:: https://travis-ci.org/jnovinger/python-livefyre.png?branch=master
        :target: https://travis-ci.org/jnovinger/python-livefyre

.. image:: https://pypip.in/d/python-livefyre/badge.png
        :target: https://crate.io/packages/python-livefyre?version=latest


API wrapper for Livefyre v3

* Free software: BSD license

Features
--------

* Implements the following Livefyre LiveComments v3 APIs:
    * Ping to Pull (profile)
    * Register Profile Interface URL
    * Create Collection




History
-------

0.1.2 (2014-01-20)
++++++++++++++++++

* Fixes broken imports introduced in PyJWT v0.1.7 by pinning to 0.1.6.

0.1.2 (2014-01-15)
++++++++++++++++++

* Detect if '.fyre.co' in `network` and remove accordingly
* Dial down the URL validation for `ping_to_pull` to handle the non-standard format
* Add a `Livefyre.list_sites` method to list as sites and auth credentials for the network
* Fix `livefyre._create_auth_token` to properly accept a `display_name` parameter
* Remove some debug `print` calls and add some documentation

0.1.1 (2014-01-14)
++++++++++++++++++

* Fix broken installs due to poorly writtens setup.py

0.1.0 (2014-01-14)
++++++++++++++++++

* First release on Github.
* Implements the follow Livefyre APIs:
    * Ping to Pull
    * Register Profile Pull Interface
    * Create Collection
pg_raxarchive 1.1
Command line tool to handle Postgresql WAL archiving on Rackspace's cloudfiles.
License: BSD

pg_raxarchive
=============

``pg_raxarchive`` is a command line tool to handle Postgresql WAL archiving on
Rackspace's cloudfiles.


Quick help
----------

Install using pip then:

- Create a file ``/etc/pg_raxarchive.ini`` with rackspace credentials (see below).
- Run ``pg_raxarchive upload {path_to_file} {basename}`` to upload archive a file.
- Run ``pg_raxarchive download {basename} {path_to_file}`` to download an archived file.
- Run ``pg_raxarchive cleanup {filename}`` to remove WAL files older than {filename}.

Rackspace credential file follows pyrax format::

    [rackspace_cloud]
    username = YUOR_USERNAME_HERE
    api_key  = YOUR_API_KEY_HERE

You can customize the region and the container name using:

- ``pg_raxarchive --container CONTAINE_RNAME ...``
- ``pg_raxarchive --region REGION_NAME ...``

By default ``pg_raxarchive`` expects to be running inside rackspace network. If this is
not your case or you want to be billed for some other reasons use ``pg_raxarchive --use-public``.


More
----

* Run ``pg_raxarchive --help`` to know more.
* Check the repository at https://github.com/duilio/pg_raxarchive/