You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To allow people to use plonecli command like build and serve in existing packages, we could provide an init command which will prepare a directory for plonecli.
We basically need a bobtemplate.cfg in the root directory of a package or buildout.
We should ask for a bobtemplate name like addon and write it to the bobtemplate.cfg.
The template name should be a list of existing templates, comming from the plonecli registry.
It has to be the global name, 'plone_addon' not just 'addon'.
Because the configuration is for mrbob and not only for bobtemplates.pone.
The command can be used then like:
plonecli init mybuildout
or just without a directory, for the current directory
plonecli init
also we need to update configure.zcml files to have the placeholder lines, where we inject config.
The text was updated successfully, but these errors were encountered:
To allow people to use plonecli command like build and serve in existing packages, we could provide an init command which will prepare a directory for plonecli.
What it needs is documented here:
https://bobtemplatesplone.readthedocs.io/en/latest/upgrade-packages.html#bobtemplate-cfg
We basically need a bobtemplate.cfg in the root directory of a package or buildout.
We should ask for a bobtemplate name like addon and write it to the bobtemplate.cfg.
The template name should be a list of existing templates, comming from the plonecli registry.
It has to be the global name, 'plone_addon' not just 'addon'.
Because the configuration is for mrbob and not only for bobtemplates.pone.
The command can be used then like:
or just without a directory, for the current directory
also we need to update configure.zcml files to have the placeholder lines, where we inject config.
The text was updated successfully, but these errors were encountered: