plaster-pastedeploy 0.3

Usage

Applications should use plaster_pastedeploy to load settings from named sections in a configuration source (usually a file).

• Please look at the documentation for plaster on how to integrate this loader into your application.

• Please look at the documentation for PasteDeploy on the specifics of the supported INI file format.

Most applications will want to use plaster.get_loader(uri, protocols=['wsgi']) to get this loader. It then exposes get_wsgi_app, get_wsgi_app_settings, get_wsgi_filter and get_wsgi_server.

import plaster

loader = plaster.get_loader('development.ini', protocols=['wsgi'])
# to get any section out of the config file
settings = loader.get_settings('app:main')

# to get settings for a WSGI app
app_config = loader.get_wsgi_app_settings() # defaults to main

# to get an actual WSGI app
app = loader.get_wsgi_app() # defaults to main

# to get a filter and compose it with an app
filter = loader.get_wsgi_filter('filt')
app = filter(app)

# to get a WSGI server
server = loader.get_wsgi_server() # defaults to main

# to start the WSGI server
server(app)

Any plaster.PlasterURL options are forwarded as defaults to the loader. Some examples are below:

• development.ini#myapp

• development.ini?http_port=8080#main

• pastedeploy+ini:///path/to/development.ini

• pastedeploy+ini://development.ini#foo

• egg:MyApp?debug=false#foo

0.3 (2017-06-02)

• Drop the ini scheme and replace with file+ini and pastedeploy. Also rename ini+pastedeploy and egg+pastedeploy to pastedeploy+ini and pastedeploy+egg respectively. See https://github.com/Pylons/plaster_pastedeploy/pull/4

0.2.1 (2017-03-29)

• Fix a bug in 0.2 in which an exception was raised for an invalid section if the a non-config-file-based protocol was used.

0.2 (2017-03-29)

• No longer raise plaster.NoSectionError exceptions. Empty dictionaries are returned for missing sections and a user should check get_sections for the list of valid sections.

0.1 (2017-03-27)

• Initial release.