Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not use own skeletons here, but use cookiecutter-zope-instance #39

Open
jensens opened this issue Jan 11, 2022 · 3 comments
Open

Do not use own skeletons here, but use cookiecutter-zope-instance #39

jensens opened this issue Jan 11, 2022 · 3 comments
Labels
04 type: enhancement making existing stuff better 13 prio: normal needs a fix, but not now

Comments

@jensens
Copy link
Sponsor Member

jensens commented Jan 11, 2022

This cookie-cutter were made for this task, here we have everything twice in several skeleton files.
I think this could be much more streamlined using the cookiecutter-zope-instance - and while at it improve it (I can move it to plone or collective).

The cookie-cutter would need to be installed in the build step together with cookiecutter script.
At startup it can generate the configuration (it takes only some millis).
It is documented (vs. the current READMe has many bugs and is consfusing)

This could probably also help using the image for development.

@jensens jensens added 04 type: enhancement making existing stuff better 13 prio: normal needs a fix, but not now labels Jan 11, 2022
@jensens
Copy link
Sponsor Member Author

jensens commented Nov 7, 2022

see also #69

@Rudd-O
Copy link
Contributor

Rudd-O commented Nov 7, 2022

I would not mind seeing this coded and merged. In the meantime — in the spirit of not letting the perfect be the enemy of the good — can we look into the minor config PRs queued up?

@jensens
Copy link
Sponsor Member Author

jensens commented Nov 7, 2022

Sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
04 type: enhancement making existing stuff better 13 prio: normal needs a fix, but not now
Projects
None yet
Development

No branches or pull requests

2 participants