<commit_before>Claw - Cloudify Almighty Wrapper
================================

Prerequisites
-------------
`cloudify-system-tests <https://github.com/cloudify-cosmo/cloudify-system-tests>`_
should be installed in editable mode in the relevant virtualenv.


Installation
------------
.. code-block:: sh

    pip install https://github.com/dankilman/claw/archive/master.tar.gz


Getting Started
---------------
#. Choose a location that will serve as the base directory for all ``claw``
   related configuration and generated files. For example:

    .. code-block:: sh

        export CLAW_HOME=$HOME/claw
        mkdir -p $CLAW_HOME

#. Initialize ``claw`` in the base directory. While we run ``init`` in a
   specific directory, note that initialization is only performed once,
   i.e. the init configuration will be stored in ``~/.claw`` and subsequent
   ``claw`` commands can be executed from any directory, not specifically the
   directory in which ``init`` was performed.

    .. code-block:: sh

        cd $CLAW_HOME
        claw init

The ``init`` command created two files: ``suites.yaml`` and ``blueprints.yaml``
which are covered in their own sections. It also created a directory named
``configurations`` which is where generated manager blueprint configurations
will be placed and a directory named ``scripts`` prepopulated with an example
script.

It will make sense to have the base directory managed by some version control
system (i.e. ``git``, privately, as these configuration files will probably<commit_msg>small changes<commit_after>Claw - Cloudify Almighty Wrapper
================================

Prerequisites
-------------
`cloudify-system-tests <https://github.com/cloudify-cosmo/cloudify-system-tests>`_
should be installed in editable mode in the relevant virtualenv.


Installation
------------
.. code-block:: sh

    $ pip install https://github.com/dankilman/claw/archive/master.tar.gz


Getting Started
---------------
#. Choose a location that will serve as the base directory for all ``claw``
   related configuration and generated files. For example:

    .. code-block:: sh

        $ export CLAW_HOME=$HOME/claw
        $ mkdir -p $CLAW_HOME

#. Initialize ``claw`` in the base directory. While we run ``init`` in a
   specific directory, note that initialization is only performed once,
   i.e. the init configuration will be stored in ``~/.claw`` and subsequent
   ``claw`` commands can be executed from any directory, not specifically the
   directory in which ``init`` was performed.

    .. code-block:: sh

        $ cd $CLAW_HOME
        $ claw init

The ``init`` command created two files: ``suites.yaml`` and ``blueprints.yaml``
which are covered in their own sections. It also created a directory named
``configurations`` which is where generated manager blueprint configurations
will be placed and a directory named ``scripts`` prepopulated with an example
script.

It will make sense to have the base directory managed by some version control
system (i.e. ``git``, privately, as these configuration files will probably
{'fraction_non_alphanumeric': 0.12979830839297332, 'fraction_numerical': 0.0, 'mean_word_length': 3.4500723589001447, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4499571', 'n_tokens_mistral': 811, 'n_tokens_neox': 774, 'n_words': 348}