Developer config bundle¶

Solution

The solution: have a product set all those developer settings for you and install it only on your development machine. Fine. Time to get cracking. I created a bundle to do the following:

Resource registries

portal_css and portal_javascripts are put into debug mode. Now you get the real css and javascript files (uncached) instead of plone4321.css and so.

Cachefu

Cachefu is uninstalled, that's the handiest (though brute-force) way of not sending out caching headers that can cause caching side effects.

Products that are installed

Some products are installed that you normally don't want on your production site:

• PloneErrorReporting provides more details about the error - right in your browser where they occur. It is bundled with plone, but not enabled by default.
• Clouseau gives you a very nice in-browser javascript-based python prompt.
• DocFinderTab - There is no svn source for it that I can find. Till lurker puts it in the collective (which he said he'd look into), I've just slapped the extracted tarball in here.
• enablesettrace adds the possibility to put an import pdb;pdb.set_trace() into your python scripts.

Where to get it

You can do an svn checkout of the bundle at https://svn.plone.org/svn/collective/developerconfig/bundles/plone25develop.

Instancemanager

Maurits added a setting to instancemanager (for instancemanager, also see my posts). Set development_machine = True in your userdefaults.py on your development machine. Next, add the developer config bundle to your project's bundles, but mark it as for-development-only:

symlinkbundle_sources = [
    'preu/externalproducts',
    'preu/products',
    {'source': 'preu/plone25develop',
     'develop': True},
    ]

It is that last dictionary that does the trick. Items with develop=True will only get installed on development machines.

Instancemanager is not really needed, but it can make life much easier in this case.