Re: [Zope-dev] zope.app.paste
On Thu, Dec 15, 2011 at 18:59, Jim Fulton j...@zope.com wrote: There is http://pypi.python.org/pypi/zope.app.wsgi Doh! I didn't realize that that provides paste integration. Cool. Thanks. So, does anyone know of a recipe, similar to zc.zope3recipes:instance that drives this? z3c.recipe.paster[1]. fyi, Paste and PasteScript are superseded by WebOb / PasteOb (because they hadn't Python 3 support). [1]http://pypi.python.org/pypi/z3c.recipe.paster -- Sebastien Douche sdou...@gmail.com Twitter: @sdouche / G+: +sdouche ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.paste
On 12/15/11 9:15 AM, Jim Fulton wrote: I'm going to take the liberty of creating a new package in the zope.app namespace. It's a small package that allows, zope.app-based applications to be wired up to WSGI middleware and servers using the paste-deploy framework. (Hopefully, I didn't miss something that already does this. I'm not sure where I would look for such a thing.) If anyone objects (or if this is duplicating something that already exists), please let me know. There is http://pypi.python.org/pypi/zope.app.wsgi David -- David Glick Web Developer davidgl...@groundwireconsulting.com 206.286.1235x32 Groundwire Consulting is here. http://groundwire.org/about/FAQ-gw-consulting ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.paste
On Thu, Dec 15, 2011 at 12:22 PM, David Glick davidgl...@groundwire.org wrote: On 12/15/11 9:15 AM, Jim Fulton wrote: I'm going to take the liberty of creating a new package in the zope.app namespace. It's a small package that allows, zope.app-based applications to be wired up to WSGI middleware and servers using the paste-deploy framework. (Hopefully, I didn't miss something that already does this. I'm not sure where I would look for such a thing.) If anyone objects (or if this is duplicating something that already exists), please let me know. There is http://pypi.python.org/pypi/zope.app.wsgi Doh! I didn't realize that that provides paste integration. Cool. Thanks. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.paste
On Thu, Dec 15, 2011 at 12:53 PM, Jim Fulton j...@zope.com wrote: On Thu, Dec 15, 2011 at 12:22 PM, David Glick davidgl...@groundwire.org wrote: On 12/15/11 9:15 AM, Jim Fulton wrote: I'm going to take the liberty of creating a new package in the zope.app namespace. It's a small package that allows, zope.app-based applications to be wired up to WSGI middleware and servers using the paste-deploy framework. (Hopefully, I didn't miss something that already does this. I'm not sure where I would look for such a thing.) If anyone objects (or if this is duplicating something that already exists), please let me know. There is http://pypi.python.org/pypi/zope.app.wsgi Doh! I didn't realize that that provides paste integration. Cool. Thanks. So, does anyone know of a recipe, similar to zc.zope3recipes:instance that drives this? If not, I'll add support to zc.zope3recipes. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.paste
On Thu, Dec 15, 2011 at 1:41 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
On Thursday, December 15, 2011 12:59:57 PM Jim Fulton wrote:
So, does anyone know of a recipe, similar to zc.zope3recipes:instance
that drives this?
I am using collective.recipe.template to generate different configuration
files
from a common template. Here is a snippet from my buildout file:
[DEFAULT]
input = ${buildout:paster-directory}/dev.ini.in
output = ${buildout:paster-directory}/dev.ini
sites-config-directory = ${buildout:directory}/data/sites-config/dev
mail-directory = ${buildout:var-directory}/mail
zodb-config-path = ${buildout:paster-directory}/zodb.conf
database = db
database-host = localhost
logs-directory = ${buildout:directory}/logs
web-server-host = localhost
web-server-port = 8000
[dev_ini]
recipe = collective.recipe.template
call-server = http://localhost:8000/calls/tropo
[staging_ini]
recipe = collective.recipe.template
input = ${buildout:paster-directory}/prod.ini.in
output = ${buildout:paster-directory}/staging.ini
web-server-host = staging
web-server-port = 8020
database = staging-db
How do values get from DEFAULT into the other sections?
If this is a buildout behavior, it's unintentional and unlikely to
work in the future.
Jim
--
Jim Fulton
http://www.linkedin.com/in/jimfulton
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.paste
On Thu, Dec 15, 2011 at 2:00 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
On Thursday, December 15, 2011 01:54:01 PM Jim Fulton wrote:
How do values get from DEFAULT into the other sections?
If this is a buildout behavior, it's unintentional and unlikely to
work in the future.
This is a configparser feature. The [DEFAULT] section contains options that
propagate to all other sections. Unless buildout is not using configparser in
the future, then the feature is pretty stable. :-)
buildout 2 doesn't use config parser. IIRC, there was never an
intention to support DEFAULT (except perhaps beyond some initial
prototypes).
Of course, it is no big
deal to repeat the options in every section, but that's more verbose.
You could use macros,
http://pypi.python.org/pypi/zc.buildout/1.5.2#extending-sections-macros
[dev_ini]
recipe = collective.recipe.template
call-server = http://localhost:8000/calls/tropo
input = ${buildout:paster-directory}/dev.ini.in
output = ${buildout:paster-directory}/dev.ini
sites-config-directory = ${buildout:directory}/data/sites-config/dev
mail-directory = ${buildout:var-directory}/mail
zodb-config-path = ${buildout:paster-directory}/zodb.conf
database = db
database-host = localhost
logs-directory = ${buildout:directory}/logs
web-server-host = localhost
web-server-port = 8000
[staging_ini]
= dev
input = ${buildout:paster-directory}/prod.ini.in
output = ${buildout:paster-directory}/staging.ini
web-server-host = staging
web-server-port = 8020
database = staging-db
Jim
--
Jim Fulton
http://www.linkedin.com/in/jimfulton
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
