Metadata-Version: 2.0
Name: waggle
Version: 0.2.4
Summary: Tools for a BeeKeeper worker drone to report status back to the hive.
Home-page: http://pybee.org/waggle
Author: Russell Keith-Magee
Author-email: russell@keith-magee.com
License: New BSD
Keywords: beekeeper
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Topic :: Software Development
Classifier: Topic :: Utilities
Requires-Dist: github3.py
Requires-Dist: boto3
Requires-Dist: awscli

.. image:: http://pybee.org/project/projects/tools/waggle/waggle.png
    :width: 72px
    :target: https://pybee.org/waggle

Waggle
======

.. image:: https://img.shields.io/pypi/pyversions/waggle.svg
    :target: https://pypi.python.org/pypi/waggle

.. image:: https://img.shields.io/pypi/v/waggle.svg
    :target: https://pypi.python.org/pypi/waggle

.. image:: https://img.shields.io/pypi/status/waggle.svg
    :target: https://pypi.python.org/pypi/waggle

.. image:: https://img.shields.io/pypi/l/waggle.svg
    :target: https://github.com/pybee/waggle/blob/master/LICENSE

.. image:: https://beekeeper.herokuapp.com/projects/pybee/waggle/shield
    :target: https://beekeeper.herokuapp.com/projects/pybee/waggle

.. image:: https://badges.gitter.im/pybee/general.svg
    :target: https://gitter.im/pybee/general

Prepare and upload Docker images for use by BeeKeeper.

Quickstart
----------

Create a directory, and in that directory place a `Dockerfile`, along with any
files required by the `Dockerfile`.

Optionally, you can also put an `ecs.json` file in the directory. The
`ecs.json` file should contains a JSON definition of any ECR container
settings that you want task to have. For example, if you wanted to specify a
particular memory and CPU usage profile for the task, you would specify::

    {
        memory: 50,
        cpu: 8192
    }

These settings will be used as overrides for the default container settings
used by BeeKeeper.

Then, create a file named `.env` in your current working directory that contains
the following content::

    AWS_REGION=<Your AWS region (e.g., us-west-2)>
    AWS_ACCESS_KEY_ID=<Your AWS access key>
    AWS_SECRET_ACCESS_KEY=<Your AWS secret access key>

Then, run::

    $ waggle <path to docker image directory>

This will:

* Log into AWS ECR
* Find (or create) an AWS ECR repository for your image
* Build the Docker image
* Tag the image for publication to AWS ECR
* Push the image to AWS ECR
* Register (or update) an AWS ECS task that uses the image.

If your Docker image is contained in a directory called `myimage`, your
BeeKeeper configuration will now be able to reference a task image of
`myimage`.


Testing
-------

Before you waggle your task, you're probably going to want to test it.


* To build an image locally::

    $ cd <directory with a Dockerfile in it>
    $ docker build -t <namespace>/<image> .

* To run an image locally::

    $ docker run <namespace>/<image>

  If your docker image requires environment variables (all the Beekeeper ones do),
  you may find it easier to put all those variables in a file (e.g., `.env`),
  and run::

    $ docker run --env-file=.env <namespace>/<image>

  To temporarily define a variable for the duration of the test::

    $ VARIABLE=value docker run -e VARIABLE <namespace>/<image>

  To mount a local directory as the source code directory::

    $ docker run -v `pwd`:/app/src <namespace>/<image>

* To start the container with an interactive prompt:

    $ docker run -it --env-file=.env <namespace>/<image> /bin/bash

* To clean up afterwards, run::

    $ docker ps -a

  to list all the containers that have been executed, and::

    $ docker rm $(docker ps -aq)

  to remove all the stale containers.

.. Documentation
.. -------------

.. Documentation for Waggle can be found on `Read The Docs`_.

Community
---------

Waggle is part of the `BeeWare suite`_. You can talk to the community through:

* `@pybeeware on Twitter`_

* The `pybee/general`_ channel on Gitter.

We foster a welcoming and respectful community as described in our
`BeeWare Community Code of Conduct`_.

Contributing
------------

If you experience problems with Waggle, `log them on GitHub`_. If you
want to contribute code, please `fork the code`_ and `submit a pull request`_.

.. _BeeWare suite: http://pybee.org
.. _Read The Docs: https://waggle.readthedocs.io
.. _@pybeeware on Twitter: https://twitter.com/pybeeware
.. _pybee/general: https://gitter.im/pybee/general
.. _BeeWare Community Code of Conduct: http://pybee.org/community/behavior/
.. _log them on Github: https://github.com/pybee/waggle/issues
.. _fork the code: https://github.com/pybee/waggle
.. _submit a pull request: https://github.com/pybee/waggle/pulls


