semvec/pypi-packages huggingface dataset:
templer.localcommands 1.0b2
Templer system framework for local commands
License: MIT

.. contents::

Introduction
============

This package provides the framework for local commands within the templer
system. In order for localcommands to be available to any templer package,
this package must be included.

In general, this is accomplished through an extra for the package, so for 
example if you wish to enable the local commands available for the templates
in the templer.plone package, you would reference the package thus::

    templer.plone[localcommands]

This flexibility allows more advanced users to use lighter, more flexible 
templates, while also supporting new users with templates that help them to 
get started more quickly.

Contributors
============

- Cris Ewing, original author

Based on code from zopeskel, contributors to which include:

- Daniel Nouri
- Tarek Ziadé
- Mustapha Benali
- Sylvain Viollon
- Alan Hoey
- Josh Johnson
- Emanuel Sartor
- Matthew Wilkes
- Joel Burton
- Cris Ewing
- Chris Calloway
- Chris Rossi

Changelog
=========

0.1b2 May 20, 2012
------------------

- Fix packaging error
  [cewing]

0.1b1 May 17, 2012
------------------

- Add TemplerLocalCommand and TemplerLocalTemplate base classes, modelled
  on the local command and template classes from zopeskel, with fixes
  [cewing]

- Add tests for local command instance methods
  [cewing]

- Package created using templer
  [cewing]
templer.zope 1.0b2
Templer system extensions for zope
License: MIT
Keywords: zope buildout

.. contents::

Introduction
============

This package extends the functionality of the templer code generation system.
It builds upon the functionality of templer.core_ and templer.buildout_, and
depends on those packages. This package provides basic support for creating
zope packages and zope buildouts. Included are packages for basic zope
packages and basic zope buildouts.

.. _templer.core: http://pypi.python.org/pypi/templer.core
.. _templer.buildout: http://pypi.python.org/pypi/templer.buildout

Creating Packages
-----------------

As with the parent package, templer.core, creating packages using
templer.zope templates is accomplished by using the ``templer`` script. The
script is invoked thus::

    templer zope2_basic

This will create a basic zope package skeleton.

Provided Templates
------------------

This package provides two templates for Zope package development

zope2_basic
    A namespace package for developing Zope2 applications.  The package comes
    complete with a simple development buildout for Zope2 in which the package
    is installed

zope2_nested
    A nested namespace package for developing Zope2 applications.  The package
    comes complete with a simple development buildout for Zope2 in which the
    package is installed

Other Functions
---------------

The ``templer`` script provides a number of other functions, these are 
described in full on the index page for templer.core_ at PyPI_

.. _templer.core: http://pypi.python.org/pypi/templer.core
.. _PyPI: http://pypi.python.org/pypi

Contributors
============

- Cris Ewing, original author

Based on code from zopeskel, contributors to which include:

- Daniel Nouri
- Tarek Ziadé
- Mustapha Benali
- Sylvain Viollon
- Alan Hoey
- Josh Johnson
- Emanuel Sartor
- Matthew Wilkes
- Joel Burton
- Cris Ewing
- Chris Calloway
- Chris Rossi

Changelog
=========

1.0b2 May 20, 2012
------------------

- Fix packaging problem
  [cewing]

1.0b1 May 17, 2012
------------------

- create buildout configuration for zope packages that will work
  [cewing]

- modify package layout for basic zope template to mimic that of the Zope
  Developers Guide (http://docs.zope.org/zope2/zdgbook/GettingStarted.html)
  [cewing]

- add a new nested zope template for a simple zope package skeleton with a 
  nested namespace
  [cewing]

- renamed basic_zope to zope2_basic to maintain consistency in entry point
  naming
  [cewing]

- add tests for zope2_nested template
  [cewing]

- updated README to reflect the new additions
  [cewing]

1.0a2 October 7, 2011
---------------------

- Metadata fixes [cewing]

1.0a1 October 7, 2011
---------------------

- Ported abstract zope package and basic zope package from zopeskel along with
  their tests [cewing]

- Package created using templer
  [cewing]
spot 0.1a
DotCloud environment loader
License: MIT

==================================
SPOT - DotCloud environment loader
==================================

Why?
====

When working with DotCloud_ you will more than likely have a developement
environment locally that offers the services your application requires which
are specified in the `build file`_.

Locally one very rarely bother changing the parameters of the services from
their defaults settings but on DotCloud_ your application must read the
`environment file`_.

Hence you end up with a fair amount of boilerplate code in your application
which figures out wether it is running locally or on DotCloud_ and instantiates
the services for you to use accordingly.

Not anymore ... if you don't want to ;)

How?
====

Enters SPOT (named after the French earth observation satellite). SPOT knows
wether your code is running locally or on DotCloud_, exposes each service
parameters under the name you gave it in your `build file`_.

For example if your build file contains a python_ service named www and a redis_
service named cache::

    www:
        type: python
    cache:
        type: redis

Then when you instantiate a spot.Dotcloud() object it will expose the cache
services::

    >>> import spot
    >>> dotcloud = spot.Dotcloud()
    >>> isinstance(dotcloud.cache, spot.Redis)
    True

When running locally::

    >>> dotcloud.cache.host
    u'localhost'

But on DotCloud::

    >>> dotcloud.cache.host
    u'SOMETHING.dotcloud.com'

If you have installed the packages allowing Python to handle the services e.g.
redis_ (and hiredis_), the spot.Dotcloud instance also expose a connection to
the server you can use out of the box::

    >>> type(dotcloud.cache.server)
    <class 'redis.client.StrictRedis'>

Next?
=====

At this stage only the Redis_ and MongoDB_ services are managed. I will add more
as I *require* them ... or you can contribute and submit new services definition
via pull request ;)



.. _DotCloud: http://dotcloud.com
.. _redis: http://redis.io
.. _python: http://python.org
.. _build file: http://docs.dotcloud.com/guides/build-file/
.. _environment file: http://docs.dotcloud.com/guides/environment/
.. _redis: http://pypi.python.org/pypi/redis
.. _hiredis: http://pypi.python.org/pypi/hiredis
.. _mongodb: http://www.mongodb.org/