semvec/pypi-packages huggingface dataset:
presstatic 0.1.0
Deploy static websites to Amazon S3 easily.
License: BSD

presstatic
----------

This is a little CLI utility that helps deploying static websites to Amazon S3.

Usage
-----

.. code-block:: shell

	$> pip install presstatic

	$> pstatic -h

	usage: presstatic [-h] [-http HOST:PORT] [-s3 bucket] directory

	positional arguments:
		directory        directory containing the static website.

	optional arguments:
		-h, --help       show this help message and exit
		-http HOST:PORT  creates an HTTP Server with <directory> as root dir.
		-s3 bucket       deploy on the specified S3 bucket.
  		
* upload your website:

.. code-block:: shell

	$> export AWS_ACCESS_KEY_ID=<Your Key id>

	$> export AWS_SECRET_ACCESS_KEY=<Your Secret>

	$> pstatic -s3 example.com ~/projects/example.com
  	
* preview your website while you develop it:

	Any change in files/directories will trigger the builder. Because of this and other reasons this http server is intended for development only.

.. code-block:: shell
	
	$> pstatic -http ~/projects/example.com


Templates
---------

We use the awesome `Jinja <http://jinja.pocoo.org/>`_ template engine.

Assets
------

We are using `webassets <https://github.com/miracle2k/webassets>`_ for asset bundling.

If you intend to use assets you need to add a configuration file (YAML) to your root project.
Please see the webassets docs to see for more details.

Here's an example:

.. code-block:: yaml

	url: /static
	debug: True
	bundles:
	    all_css:
	        filters: yui_css
	        output: static/css/packed.css
	        contents:
	            - static/css/style.css
	            - static/css/jquery.fancybox.css
	    all_js:
	        filters: yui_js
	        output: static/js/packed.js
	        contents:
	            - static/js/jquery-latest.min.js
	            - static/js/jquery.fancybox.pack.js
	            - static/js/app.js

TODO
----

* Add Template support [DRAFT]
* Add Asset support [DRAFT]
* Add watcher support [DRAFT]
* Upload only modified files [DONE]
declare-amqp 0.0.4
A way to declare your AMQP exchanges, queues, and bindings outside of the application
License: BSD
Keywords: amqp

# Declare AMQP

A way to declare your exchanges, queues, and bindings outside of the application

## Installing

    pip install declare-amqp

## Declaration

You can see the extend of configuration in the `example_config.yml` file. All
fields used are currently required except for the `arguments` on exchanges.

    exchanges:
      - name: example_exchange
        type: direct
        durable: True
        auto_delete: False
        arguments:
          alternate-exchange: your_alternate_exchange

    queues:
      - name: test_queue
        auto_delete: False
        durable: True
        bindings:
          - exchange: example_exchange
            binding_key: test_binding

When I have the need for them exchange-to-exchange bindings will be added.

## Running

### ENVVARS

    AMQP_HOST (default: localhost)

    AMQP_USER (default: guest)

    AMQP_PASS (default: guest)

    AMQP_VHOST(default: /)


### CLI

Once you have set the envvars you are set to run `declare-amqp`

    declare-amqp --config your_config.yml
mr.sisyphus 1.0
His pointless toil will never end
License: BSD

mr.sisyphus
===========

*His pointless toil will never end.*

Mr. Sisyphus is a tool to improve the permissions for github organisations. It will allow users to create repositories without having to made admins of repositories. It requires an organisation in GitHub with three teams. 

* The Owners team is created by default
* A team that holds all the developers in the organisation, with Push and Pull rights set
* A new team for this package that has Push, Pull and Admin rights set.
 
This new team should **not** be administered by the organisation admins, they should just administer the Owners and Developers teams.

Usage
-----

You will need to customise the `mr.sisyphus.cfg` file with information about your organisation. A default is provided for the organisation `collective`. In this organisation the teams listed above are named, respectively:

* Owners
* --auto-contributors
* CanAdd

therefore the configuration file looks like::

    [sisyphus]
    organization = collective
    developer_team = --auto-contributors
    stub_team = CanAdd

The first time you run the script it will prompt for your GitHub username and password. The user you authenticate as **must** be a member of the Owners team in the organisation you want to administer. It will then create an OAuth token and store it in the mr.sisyphus.cfg file. From this point on the configuration file should be considered secret, as there is no way to get an OAuth token that applies just to one organisation. If someone finds this token they'd gain admin access to your private repos. The OAuth token can be disabled from your GitHub user profile, but you won't be prompted to log in again unless you delete it from the config file.

From this point on the script can be run in non-interactive mode

Dry Run
-------

To see what mr.sisyphus is planning to do invoke it as `./bin/mr.sisyphus.cfg -n` and it will skip making the actual calls to github.
django-autoroot 0.2.1
automaticly creates `root` user after syncdb if not exists
License: BSD
Keywords: django user create syncdb

After syncdb's signal is called, root user is created (if not exists).
Default settings creates root:root@localhost:qqq user, but
you can customize it in settings by::

    AUTOROOT_NAME
    AUTOROOT_EMAIL
    AUTOROOT_PASSWORD


You can tell to create superuser only in DEBUG mode by changing variable below,
in `settings.py`::

    AUTOROOT_DEBUG_ONLY (default True)


Code is stolen from:
http://djangosnippets.org/snippets/1875/