Piano. Beginner friendly Plone development.
Project description
piano
Piano. Beginner friendly Plone development.
Installation
Prerequisites
You should have the build tools and Plone dependencies installed. For example on debian or Ubuntu you will need to run the following:
apt-get install build-essential libssl-dev libxml2-dev libxslt1-dev libbz2-dev zlib1g-dev -y apt-get install python-setuptools python-virtualenv libjpeg62-dev wv poppler-utils -y
Quick Install
To install piano quickly, run the following commands:
wget -qO- goo.gl/NmFSel | bash source ~/.bashrc
This will use pipsi to install the relevant packages in user space. It also ensures that piano is using the most up-to-date version of setuptools.
Longer Install
We prefer and recommend pipsi.
Once you have pipsi, run:
pipsi install for-beginner-piano ~/.local/venvs/for-beginner-piano/bin/pip install -U setuptools
Usage
To create a new Plone buildout project
Use the subcommand newbuildout to create a buildout project.
For example, if your project will be called my-plone-site:
piano newbuildout my-plone-site
You’ll see output similar to this:
Creating virtualenv... (my-plone-site) Installing Buildout... Downloading installer (https://launchpad.net/plone/4.3/4.3.3/+download/Plone-4.3.3-UnifiedInstaller.tgz) Unpacking installer... Unpacking cache... Installing eggs... Installing cmmi & dist... Configuring cache... Running Buildout...
Creating a Plone add-on
This is not working yet, but:
piano newaddon myaddon
(coming soon, this command doesn’t work yet)
Credits
piano is created and managed by David Bain, it is built on top of plock which was created and maintained by Alex Clark.
Changelog
0.2.15 (2015-02-02)
fixed flake8 issues
0.2.14 (2015-02-02)
looks for unified installer in the ~/.buildout cache first. does not re-download unified installer
0.2.12 (2015-02-02)
made adjustments to README
0.2.3 (2015-02-02)
added MANIFEST.in
added README and CHANGES to long description of setup.py
0.2.2 (2015-02-02)
now unpacks unified installer cache to ~/.buildout/
creates ~/.buildout/default.cfg file
keeps a cache based on settings in default.cfg, cache is, by default ~/.buildout/[eggs|downloads|extends-cache]
0.2.1 (2015-02-01)
fix broken release
0.2.0 (2015-02-01)
added and documented quick install script
added Change log
0.1.0 (2015-02-01)
Initial release