Placing your Grok project under version control
Registered by
Steve Schmechel
Doc review project
Blueprint information
- Status:
- Not started
- Approver:
- Grok Doc
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
2009-09-30 == Marked as possibly outdated == /jhsware
2009-xx-xx
Is the site.zcml for Zope sites (or Grok) sites always the same? If it is modified isn't it reflecting some part in the applications code, f.i. in the case of @require decorators? In that case it would perhaps be prudent to include zcml configuration information in version control.
- I am well aware that site.zcml and authentication code like @grok.require decorators fall outside the scope of project under version control, and Zope/Grok authentication is way too complex to be secure anyway, so this might well be beside the point -
(?)
