collective.autorestart 0.1

Automatically reloads changed code into Plone when you edit Python files

collective.autorestart

Automatically reload chanhed Python files - putting agility back to Plone development.

collective.autorestart detects changes in Plone codebase and reloads changed code files automatically. collective.autorestart uses plone.reload package to perform the actual reload.

Currently file system is monitored using inotify interface and the support is only available for Linux. The future versions will support other operating systems as long as somebody contributes the file system monitoring interface or gives the author a new computer.

Features

• Recursively detect changes in ZCML and Python files which are registered to PYTHONPATH

• Automatically trigger reload when files are changed (saved)

• Audio playback depending on whether the restart succeed or failed

Dependencies

• plone.reload

• pyinotify for monitoring files.

• pygame for audio playback (optional)

pyinotify relies on Linux kernel feature called inotify and thus this application only works on Linux currently. However, it should be trivial to port it for other platforms.

Installation

pyinotify depends on ctypes package and currently (04/2009) ctypes package is broken in PyPi. Manual installation needed:

wget http://kent.dl.sourceforge.net/sourceforge/ctypes/ctypes-1.0.2.tar.gz
tar -xzf ctypes-1.0.2.tar.gz
cd ctypes-1.0.2/
python2.4 setup.py build
sudo python2.4 setup.py install

Add the following egg to your buildout.cfg.

eggs =

collective.autorestart

…

zcml =

collective.autorstart

Rerun buildout. Answer yes when pygame barks about missing libraries.

Adding sound effect support

Optionally pygame egg is needed for sound support. Pygame depends on SDL development library:

sudo apt-get install libsdl1.2-dev libsdl-mixer1.2-dev

Add the following egg to your buildout.cfg:

eggs =
        pygame

Rerun buildout.

Usage

Start Plone normally in the foreground using command:

bin/instance fg

collective.autorestart might not be effective immediately, since its sets monitor on many files on background. When it starts, you’ll see a message in your terminal:

collective.autorestart Monitoring 3477 paths 12591 files for changes

Edit any Python files. When you press save you should output in your terminal:

2009-04-15 04:11:37 INFO collective.autorestart Detected file system change:/home/moo/workspace/y-trunk/x/browser/views.py/
2009-04-15 04:11:37 INFO collective.autorestart Reloading Plone
2009-04-15 04:12:06 INFO collective.autorestart Reloaded done, report:Code reloaded:

        ...x/browser/views.py

If you have pygame installed you will also hear a sound effect depending on whether code reload succeeded or failed.

Knowns issues

• Sometimes Zope process seem to fall into Zombie state (kind of dead, but blocks the HTTP port). In this case, manually kill Zope.

• New files are not automatically picked up

• If you quickly edit and save several files some changes might go unnoticed

• ZCML autoreload is currently disabled (bgthread.reload_plone) since it seems to break zope.schema vocabularies

• Something (some editors) are keen to fire double modify events on file changes

Author

Mikko Ohtamaa

Twinapex Research, Oulu, Finland - High quality Python hackers for hire

Changelog

0.2

• Revamped old plonemon codebase