plone / plone/plonecli

Include instance, zeoserver and zeopack commands

Open
#10 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

99 tag: wontfix
Dominant language
Python
Stars
20
Forks
12
PR merge metrics
No merged PRs in 30d

Description

This is nothing to hurry, but I leave this here for discussion.

But at some timeframe, how about including instance, zeoserver and zeopack commands from plone.recipe.zope2instance and plone.recipe.zeoserver (when plonecli is installed with the rest of Plone).

https://github.com/plone/plonecli/commit/c6dd010e2a5c6268842e7d81f743451c3c7dd57b

I've been experimenting about installing and running Plone without buildout and the missing part was getting the familiar scripts out of buildout recipes. I saw that cli already had "serve" command, so why not the rest.

Obviously, also generating zope.conf and instance skel might be good fit for plonecli (only dir with ./etc/site.zcml and zope/zeo.conf seems to be really needed in minimal setup), but maybe later.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked commit and the existing plonecli "serve" command. Clarify which instance, zeoserver, and zeopack behavior is required, including whether zope.conf and the instance skeleton are in scope; done means the agreed commands are available when plonecli is installed with Plone.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.