Skip to content
Plone Command Line Client - for creating and working with custom add-ons and themes
Python Makefile Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github init Oct 21, 2017
docs Add test command to allow running test from plonecli Apr 3, 2018
plonecli Cleanup Apr 14, 2019
tests fix dublicate test name Apr 14, 2019
.editorconfig
.gitignore Iupdate jsconfig and gitignore file Oct 17, 2018
.travis.yml
AUTHORS.rst update changelog Mar 22, 2018
CHANGES.rst
CONTRIBUTING.rst Add test command to allow running test from plonecli Apr 3, 2018
LICENSE init Oct 21, 2017
MANIFEST.in prepare release Mar 22, 2018
Makefile init Oct 21, 2017
README.rst Update the list of entry points Apr 18, 2019
jsconfig.json
plonecli.rst
plonecli_autocomplete.sh provide plonecli_autocomplete.sh for bash autocompletion, fix depency… Oct 30, 2017
setup.cfg
setup.py prepair release Apr 14, 2019
tox.ini Add build option -p to define python binary to use for virtualenv Apr 14, 2019

README.rst

https://secure.travis-ci.org/plone/plonecli.png?branch=master Coveralls Latest Version

PyPI - Python Version

Plone CLI

A Plone CLI for creating Plone packages

The Plone CLI is meant for developing Plone packages, we will not add functions to install or run Plone in production. For this we should build another package, let's say *plonectl which will provide installing and deployment functions. It also support's GIT by default, to keep track of changes one is doing with the templates.*

Installation

We install plonecli in the global user site-packages, so that we can use it in multiple projects.

Versions newer than 0.1.1b4 are installable like any other package with pip:

$ pip install plonecli --user
$ plonecli -l

To upgrade plonecli just do:

$ pip install -U plonecli --user
Note: Make sure that the install directory is in $PATH ( e.g. export PATH=$PATH:$HOME/.local/bin/  )

NOTE: We are now using a the ORIGINAL version of the CLICK library, please uninstall plonecli-click before you install the new version of plonecli.

If would like to use plonecli with pipenv, you can do it as follow:

$ mkdir cli
$ cd cli
$ pipenv install plonecli
$ pipenv shell
$ plonecli -l

Bash Auto Completion

To enable auto completion plonecli provides the plonecli_autocomplete.sh script, put the following bash command into your bashrc:

If you installed plonecli in user global packages:

$ . ~/.local/bin/plonecli_autocomplete.sh

If you installed plonecli in a virtualenv it's:

$ . /path/to/your/virtualenv/bin/plonecli_autocomplete.sh

If you used pipenv to install plonecli, you have to find out the path to the virtualenv before:

$ pipenv --virtualenv
/home/maik/.local/share/virtualenvs/pe-WnXOnVWH
. /home/maik/.local/share/virtualenvs/pe-WnXOnVWH/bin/plonecli_autocomplete.sh

Documentation

Full documentation for end users can be found in the "docs" folder, this will be available in the Plone docs at some point.

Note: you can set default answers for mr.bob questions, see bobtemplates.plone README.

Usage

Available Commands

$ plonecli --help
Usage: plonecli [OPTIONS] COMMAND1 [ARGS]... [COMMAND2 [ARGS]...]...

  Plone Command Line Interface (CLI)

Options:
  -l, --list-templates
  -V, --versions
  -h, --help            Show this message and exit.

Commands:
  build         Bootstrap and build the package
  buildout      Run the package buildout
  config        Configure mr.bob global settings
  create        Create a new Plone package
  debug         Run the Plone client in debug mode
  requirements  Install the local package requirements
  serve         Run the Plone client in foreground mode
  test          Run the tests in your package
  virtualenv    Create/update the local virtual environment...

Creating A Plone Add-on

$ plonecli -l
Available mr.bob templates:
- addon
 - behavior
 - content_type
 - portlet
 - theme
 - theme_barceloneta
 - view
 - viewlet
 - vocabulary
- buildout
- theme_package [deprecated] >> Please use the theme_barceloneta subtemplate!

$ plonecli create addon src/collective.todo

Adding Features To Your Plone Add-on

You can add different features through subtemplates. You can use them also multiple times to create different features of the same type, like two different content types.

$ cd collective.todo

$ plonecli add behavior
$ plonecli add content_type
$ plonecli add theme
$ plonecli add view
$ plonecli add viewlet
$ plonecli add vocabulary

Build Your Package

$ plonecli build

This will run:

$ virtualenv .
$ ./bin/pip install -r requirements.txt --upgrade
$ ./bin/buildout

in your target directory.

You can always run the 3 steps explicit by using virtualenv, requirements, buildout instead of build. If you want to reset your build use the --clean option on build. This will clear your virtualenv before installing the requirements and also running buildout with -n to get the newest versions.

Run Your Application

$ plonecli serve

Run Tests for Application

$ plonecli test

or run specific tests:

$ plonecli test -t test_the_thing

or run all tests including Robot tests:

$ plonecli test --all

Combining Commands

You can combine the steps above like this:

$ plonecli create addon src/collective.todo build test --all serve

Developer Guide

Setup Developer Environment

$ git clone https://github.com/plone/plonecli/
$ cd plonecli
$ virtualenv .
$ source bin/activate
$ pip install -r requirements.txt
$ python setup.py develop
$ plonecli --help

Running Tests

You can run the tests using the following command:

$ tox

or by installing py.test and run the test directly without tox:

$ py.test test/

or a single test:

$ py.test test/ -k test_get_package_root

Register Your Bobtemplates Package For Plonecli

All mr.bob templates can be registered for plonecli by adding an entry_point to your setup.py.

Here are the entry_points of the bobtemplates.plone package:

entry_points={
    'mrbob_templates': [
        'plone_addon = bobtemplates.plone.bobregistry:plone_addon',
        'plone_buildout = bobtemplates.plone.bobregistry:plone_buildout',  # NOQA E501
        'plone_theme_package = bobtemplates.plone.bobregistry:plone_theme_package',  # NOQA E501
        'plone_content_type = bobtemplates.plone.bobregistry:plone_content_type',  # NOQA E501
        'plone_view = bobtemplates.plone.bobregistry:plone_view',
        'plone_viewlet = bobtemplates.plone.bobregistry:plone_viewlet',
        'plone_portlet = bobtemplates.plone.bobregistry:plone_portlet',
        'plone_theme = bobtemplates.plone.bobregistry:plone_theme',
        'plone_theme_barceloneta = bobtemplates.plone.bobregistry:plone_theme_barceloneta',  # NOQA E501
        'plone_vocabulary = bobtemplates.plone.bobregistry:plone_vocabulary',  # NOQA E501
        'plone_behavior = bobtemplates.plone.bobregistry:plone_behavior',  # NOQA E501
        'plone_restapi_service = bobtemplates.plone.bobregistry:plone_restapi_service', # NOQA E501
    ],
},

The entry_point name is used as the global template name for mr.bob. You also need to provide a bobregistry.py file with a method for each entry_point, it should be named after the entry_point name:

# -*- coding: utf-8 -*-

class RegEntry(object):
    def __init__(self):
        self.template = ''
        self.plonecli_alias = ''
        self.depend_on = None
        self.deprecated = False
        self.info = ''


# standalone template
def plone_addon():
    reg = RegEntry()
    reg.template = 'bobtemplates.plone:addon'
    reg.plonecli_alias = 'addon'
    return reg


# sub template
def plone_theme():
    reg = RegEntry()
    reg.template = 'bobtemplates.plone:theme'
    reg.plonecli_alias = 'theme'
    reg.depend_on = 'plone_addon'
    return reg

For every template you add a line to the entry_points and define a method in the bobregistry.py, which will return a registry object with some properties.

  • template - contains the name of the actual mr.bob template.
  • plonecli_alias - defines the name under which the template will be used inside plonecli
  • depend_on:
    1. for a standalone template, the depend_on property is None
    2. for a sub template, the depend_on contains the name of the parent standalone template, usualy addon.
  • deprecated - boolean saying whether this templates is deprecated and will be removed in future releases
  • info - message that will be shown next to the template when the template is deprecated

Contribute

License

This project is licensed under the BSD license.

You can’t perform that action at this time.