Paster templates for standard NiteoWeb Plone projects
Starting, deploying and maintaining Plone 4 projects made easy
zopeskel.niteoweb is collection of ZopeSkel templates to help you standardize and automate the task of starting, deploying and maintaining a new Plone project. Its particularly helpful for less experienced Plone developers as they can get a properly structured and deployed Plone 4 project in no time. A complete tutorial on how to use these templates for your own projects is at http://ploneboutique.com.
It will help you to automate and standardize:
Starting a new Plone 4 project that includes old- and new-style python, zope page template and css overrides, collective.xdv, etc.
Adding your own functionalities and look to Plone 4.
Staging and deploying your Plone 4 project on Rackspace Cloud server instance running CentOS, with Nginx in front and secured with iptables firewall (only $11 per month per instance!)
Maintaining and upgrading your Plone 4 project on the production server.
By default the Plone 4 project you create with these templates is equiped with:
latest collective.xdv with sample rules.xml and template.html,
.svnignore files to ignore files/folders that should not be stored inside your code repository,
base.cfg that holds global configuration for your buildout,
versions.cfg that pins all your eggs to specific versions to ensure repeatability,
development.cfg that builds a development environment,
production.cfg that builds a production environment with ZEO,
sphinx.cfg that is used to generate documentation for your code,
test_setup.py that shows you how to write tests for your project,
fabfile.py with Fabric commands to automatically deploy your code and data to a Rackspace Cloud server instance running CentOS,
Sphinx documentation for your project,
nginx.conf template to setup the Nginx web-proxy in front of your Zope,
basic iptables configuration to deny access on all ports but the ones you actually use,
munin-node.conf template to setup Munin system monitor node on your production server,
and much more.
Installation is simple, just run ‘sudo easy_install zopeskel.niteoweb’ and you’re good to go. Go where? To http://ploneboutique.com.
Out-of-the-box, this package is intended for NiteoWeb’s internal projects. However, at http://ploneboutique.com you’ll find a comprehensive guide on how to use these templates for your own projects.
add munin plugins for Zope and Nginx
yum-security email notification
per-version separation of documentation on packages.python.org
test coverage plugin for Hudson
properify version extraction in conf.py
add docstrings to Fabric commands
Nejc ‘zupo’ Zupan, NiteoWeb Ltd.
Domen ‘iElectric’ Kozar, NiteoWeb Ltd.
Automatically add project to Hudson. [iElectric]
Beautifying guide content, adding screenshots, polishing. [zupo]
Added Hudson. [iElectric]
Importing docstrings from fabfile.py into Sphinx. [iElectric]
Writing the actual guide. [zupo]
Big cleanup, based on real-life experience on using these templates. [zupo]
Went through the whole procedure and tested that it works. [zupo]
Fix supervisord runtime error. [zupo]
Debugging and cleanup. [zupo]
Refactored maintenance_hostname to headquarters_hostname. [zupo]
Added sendmail installation with Fabric. [zupo]
Hidden some ZopeSkel questions. [zupo]
Added ‘maintenance_ip’ question. [zupo]
Ask for maintenance username when starting Fabric commands. [zupo]
Many fixes to templates. [zupo]
Pin down a specific version of Fabric. [zupo]
Moved global config, Fabric and zest.releaser to production.cfg. [zupo]
Changed comment banner styling. [zupo]
Moved actual code into ./src. [zupo]
Changed default IP. [zupo]
Added Quick-start information. [zupo]
Fixed sintax errors in production.cfg_tmpl [zupo]
Added documentation structure. [zupo]
Added zc.buildout and Sphinx. [zupo]
Added zest.releaser to buildout [zupo]
Added initial documentation. [zupo]
Initial release. [zupo]
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.