bcwaldon/cloudenvy — pull request #16 by termie (2012-07-30 23:16:08+00:00)
Title: refactor code into separate files, change model

this switches to the discussed cloud -> template -> instance model.

now you can say:

envy up -n termie1
envy up -n termie2

and have two running instances of the default templates (cloud:envy,
termplate:envy)

if you have multiple templates or clouds defined you can specify them
with -t and -c, respectively.

examples are updated in the cloudenvy.example file

configs are now looked for in CLOUDENVY_CONFIG (defaults to
~/.cloudenvy) and ./.cloudenvy with the second possibly overriding the
first.

once you've updated the code to this, you can just change the names of
the sections in .cloudenvy to get it working again as before.

you'll also need to run python setup.py develop again as the bin file
has changed to be auto-generated by setuptools