Must@p Zone

memmon and collective.recipe.supervisor

Sat, 6 Jun 2009 17:00:49 +0000

I just saw a tweet advising to pin supervisor egg to 3.0a4 for those who use collective.recipe.supervisor with memmon (Memmon is moved from supervisor 3.0a7 and added to the superlance plugin). Don't do that. The 3.0a7 introduced new commands (reread, update and avail) and many improvements and fixes that will make your life easier.

You don't need to pin supervisor to 3.0a4. The collective.recipe.supervisor has already a plugins option. The ONLY change you have to make to your current buildout configuration file is to add superlance to the plugins option:



[buildout]



...



[spvisor]

recipe = collective.recipe.supervisor



...



plugins = superlance



...

and then run:



$ ./bin/buildout -v install spvisor

That's all.

Pinning buildout's picked eggs

Sun, 15 Mar 2009 11:32:46 +0000

When using a zc.buildout based deployment system you want to be able to reproduce the same setup with the same set of egg versions one month later. Without pinning all eggs picked by zc.buildout the task is impossible.

buildout.dumppickedversions is a buildout extension that does just that. It can print or generate a versions.cfg file with all eggs picked by zc.buildout.

The 0.2 release is the result of some feedback I got especially from Martin.

On how to use it see: http://pypi.python.org/pypi/buildout.dumppickedversions

Try it and give some feedback.

Login as another user without a password

Tue, 13 Jan 2009 08:56:55 +0000

Recently we developed an Intranet site with many custom workflows and roles that control what an user can see/do globally on the site and locally on some sections.

Users are stored in an AD server.

A problem we ran into was sometime we get a question like: I cannot do this or that thing. what's wrong?

The easiest way to answer this question is to login with the user's login name and password and see what is happening. Well, not really. We don't need the password. The login name is sufficient.

In the ZMI create a python script with this line:



context.acl_users.session.setupSession(

                  the_user_login_name_i_want_to_login_as,

                  context.REQUEST.RESPONSE)

Click the test tab and you are in as that user.

IMPORTANT SECURITY NOTE: Remove the script as soon as you are logged in.

Agile Project Management: Lessons Learned at Google

Sun, 20 Jul 2008 13:41:43 +0000

Jeff Sutherland the Co-Creator of the Scrum Agile Development Process is talking about Google's first Scrum implementation. If you have some free time (1h 8min) this video is good to watch: http://www.infoq.com/presentations/Agile-Management-Google-Jeff-Sutherland

Adjusting options in buildout

Tue, 10 Jun 2008 19:15:47 +0000

The configuration syntax in the new version of zc.buildout is extended with two operators += and -= to allow adjusting options in an extended profile. This is very helpful. You don't need anymore to overwrite an option in the base configuration when all you want is to remove/add an entry.

here is an example:



# base.cfg file

[buildout]



parts =

    part1

    part2



eggs =

    eggs1

    eggs2

    eggs3

To add new part and remove egg2 in an extended configuration, we do:



# newconfig.cfg file



[buildout]

extends = base.cfg



parts +=

    part3



eggs -=

    eggs2

Running buildout, the result will be as if you have run it with this configuration file:



[buildout]

parts =

    part1

    part2

    part3



eggs =

    egg1

    eggs3

That's it.
If you want to add new egg to all your profiles all you have to do is to add it to the base.cfg.

Shebang max. length

Sun, 25 May 2008 15:11:26 +0000

This may save someone's time.

If you get an error like this when running ./bin/buildout:

bash: bin/buildout: /home/mustapha/workspace/collective.buildbot/test/parts/buildslave/customer.pr: bad interpreter: Permission denied

Pay attention: the full path to the used python is truncated here.

that means that the shebang line (the first line in the bin/buildout script starting with #!) is too long. The maximum length of a shebang line is system dependent. On my Ubuntu the maximum length is 80. This table lists the maximum length of the shebang line per OS

collective.recipe.supervisor: now accepts arguments

Fri, 23 May 2008 15:44:45 +0000

Now one can add arguments to the command controlled by supervisor. You have to give all arguments between [] like this: [arg1 arg2 arg3]. ~~This way one can use ctl scripts generated by other recipes and give them the appropriate argument to make them run in foreground~~. An example:



[buildout]

parts = 

   instance1 

   supervisor



[instance1]



...



[supervisor]

recipe = collective.recipe.supervisor

port = 9001

user = mustapha

password = secret

serverurl = http://supervisor.mustap.com



programs =

 10 instance1 ${buildout:bin-directory}/instance1 [fg] ${instance1:location}

 10 instance1 ${instance1:location}/bin/runzope ${instance1:location}

 20 myprog /mypath/bin/myprog [-n 100] /mypath

For more info: http://pypi.python.org/pypi/collective.recipe.supervisor

UPDATE: After a discussion with Chris Mc Donough, I updated this post. For zope instances and zeo instances, please use the runzope and runzeo scripts instead of instance and zeo

A buildout recipe to install supervisor

Thu, 22 May 2008 08:43:33 +0000

The collective.recipe.supervisor is buildout recipe that helps with the install and configuration of supervisor.

How to use it: http://pypi.python.org/pypi/collective.recipe.supervisor

self.note = svn import with git

Wed, 7 May 2008 21:00:09 +0000

Let's create a project called plone.app.myproject:

$ mkdir plone.app.myproject 

$ cd !$

$ git svn init -s http://server.com/!$

The last command assumes that plone.app.myproject/trunk, plone.app.myproject/branches and plone.app.myproject/tags already exist in the svn repository.

$ git svn fetch

$ git add .

$ git commit -m 'initial import'

$ git svn dcommit

That's it. At this stage the master branch is reflecting the remote trunk.

Autoload eggs from buildout's development directories

Wed, 30 Apr 2008 19:32:47 +0000

When developing zope/plone eggs with buildout I have to edit the buildout configuration file ( in 3 places ) every time I create/delete/rename a development egg in the src directory or in other development directories (sometime I have more than one).

I have to add/delete/rename the egg in the eggs option of the [buildout] and then add/delete/rename the egg path in the develop option of the [buildout] and in the end add/delete/rename the zcml option of the zope [instance] or in the configure.zcml file of my policy package. This is too much specially when the speed is set to development mode. I need a less boring way to develop.

Solution

buildout.eggtractor is a buildout extension that scans the src directory or a list of directories I give for eggs and picks them up automatically. So no more editing of the buildout's configuration file.

When buildout.eggtractor finds an egg in the scanned directory it:

adds the egg to the eggs option of all zope instance parts or to a set of given parts

adds the egg's path in the develop option of the [buildout]

If tractor-autoload-zcml is not set to false, scans the egg folder for configure.zcml, meta.zcml and overrides.zcml and adds the appropriate zcml entries to the zcml option of the zope instance parts or to a set of given parts.

This steps are done on the fly when running buildout. So I can add/delete/rename an egg and it will be picked up.

NOTE: The extension does not write to the buildout's configuration file.

buildout.eggtractor options

tractor-src-directory: A set of directories to scan for development eggs. Defaults to the src directory of the buildout.

tractor-target-parts: A set of parts to update their eggs option with eggs found in the tractor-src-directory. Defaults to zope instance parts if any.

tractor-autoload-zcml(boolean): Update the zcml option of tractor-target-parts with the eggs found in tractor-src-directory. Defaults to true

tractor-zcml-top: A set of eggs to load their zcml files first. Defaults to an empty set.

How to use it

Using buildout.eggtractor is very simple. As said, it is a buildout extension. All I have to do is to declare it in the extensions option:



  [buildout]

  parts =

  

  extensions = buildout.eggtractor

That's all. buildout.eggtractor will scan the src directory and do its job every time I run the buildout command.

When I have other directories I want to scan I just add an tractor-src-directory option in the [buildout] and add my directories there:



  [buildout]

  parts =

  

  extensions = buildout.eggtractor

  

  tractor-src-directory = 

                        dev-src1 

                        dev-src2

                        src

In a few cases when the priority of loading zcml files matters. I add the egg to be loaded first in the tractor-zcml-top option in the [buildout]:



  [buildout]

  parts =

  

  extensions = buildout.eggtractor

  

  tractor-src-directory = 

            dev-src1 

            dev-src2

            src

            

  tractor-zcml-top = 

            plone.app.mypackage1

If I want to add the eggs found in the development directories to the eggs option of a given set of parts, I add a tractor-target-parts option and add the parts there:



  [buildout]

  parts = instance1 instance2 instance3

  

  extensions = buildout.eggtractor

  

  tractor-target-parts = instance1 instance3

This way only instance1 and instance3 will be updated.

If I have already other way to include the zcml files (ie: z3c.autoinclude) and don't want eggtractor to generate the zcml slugs, I add an tractor-autoload-zcml option and set it to false

In most cases you will only need to add buildout.eggtractor to the extensions option of the [buildout] without any extra configuration options.

LIMITATION

The extension assumes that the egg name reflects its file system structure example: if the egg name is com.mustap.www the extension assumes that the file system structure is one of the following::

com.mustap.www/src/com/mustap/www

com.mustap.www/com/mustap/www

This is where the extension looks for configure.zcml, meta.zcml and overrides.zcml files.

If the egg name does not reflect the file system structure, the extension will ignore it.

XXX: I guess walking through the directory is better than this assumption.
In my case this is not a limitation as I choose my egg names that way.

URL

You can get it from http://pypi.python.org/pypi/buildout.eggtractor

THANKS

Martin, Wichert and Hanno for the help and feedbacks