grokproject generates hardcoded paths
Bug #325299 reported by
Uli Fouquet
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grok |
Fix Released
|
Medium
|
Uli Fouquet |
Bug Description
When running grokproject > 1.0 some generated configuration files in etc/ contain hardcoded paths.
This blocks developers from sharing code as they have no easy way to regenerate the configuration files with their local paths.
I think using a suitable buildout-recipe to (re)generate those files (especially zope.conf) would help.
Changed in grok: | |
assignee: | nobody → uli-gnufix |
importance: | Undecided → Medium |
milestone: | none → 1.0 |
status: | New → In Progress |
Changed in grok: | |
status: | In Progress → Fix Committed |
Changed in grok: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think it's odd to run paster with a generated file under parts. Now to add a WSGI middleware component people will have to change the files in etc and then re-run buildout and then use files under parts instead? Isn't that unlike any other paster-based setup where people edit them directly? Can't we avoid hardcoded paths instead of generating them?
How do modern Zope 3 and Plone buildouts do this?