Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (pypi.python.org).
Help us improve Python packaging - Donate today!

Sanitize a plone site for development use by Makina Corpus.

Project Description

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 ;))

Actions & usage

Changing all email for all users:

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

Changing all passwords

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

Changing the administrator password

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

Running a script with all security stuff removed

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

Modifiers

Running with debug

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

Giving an alternative zope configuration file

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

Specifying the plone site id

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

Specifying the admin user

./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

1.0 - 2010-04-12

  • Initial release [kiorky]
Release History

Release History

This version
History Node

1.0

Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
collective.generic.devmode-1.0.zip (27.7 kB) Copy SHA256 Checksum SHA256 Source Apr 12, 2010

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting