Introduction

This provide a script cg.devmode which can do some actions on a zope instance.

The main use is when you grab the production datafs, you 'll need to sanitize the content a little. The sanitization include changing all passwords and all emails at once.

Another use is for running scripts without any security (we just give us all rights ;))

• Svn : http://svn.plone.org/svn/collective/collective.generic.devmode/trunk/
• Developement supported by : Makina Corpus

Credits

• Planet Makina Corpus
• Contact us

Actions & usage

./bin/cg.devmode -m --mail=some@mail.foo

./bin/cg.devmode -p  --password=secret

./bin/cg.devmode -a  --password=secret

./bin/cg.devmode -r --script=</path/to/file.py>  [--script-args="String"] # equivalent of ./bin/instance run toto.py String except for security

Modifiers

./bin/cg.devmode -v [ARGS]

./bin/cg.devmode -c <CONFIGGILE>

./bin/cg.devmode -l <PLONE_SITE_ID>

./bin/cg.devmode --user <ADMIN_USER>

collective.generic.devmode Installation

To install collective.generic.devmode into the global Python environment (or a workingenv), using a traditional Zope 2 instance, you can do this:

• When you're reading this you have probably already run

  ``easy_install collective.generic.devmode``.
  

  Find out how to install setuptools (and EasyInstall) here: http://peak.telecommunity.com/DevCenter/EasyInstall

• If you are using Zope 2.9 (not 2.10), get pythonproducts and install it via:

  python setup.py install --home /path/to/instance
  

  into your Zope instance.

Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:

• Add collective.generic.devmode to the list of eggs to install, e.g.:

  [buildout]
  parts=
      ...
      cg.devmode
  ...
  [cg.devmode]
  recipe=minitage.recipe.scripts
  eggs=${instance:eggs}
      collective.generic.devmode
  scripts=cg.devmode
  extra-paths = ${instance:extra-paths}
  # in an oldschool zope2 install, zope2home/lib/python must be in extra-paths!
  

• Re-run buildout, e.g. with:

  $ ./bin/buildout
  

Changelog