Making more and more complicated instances from server dependencies installed into the minitage tree make me relying on somehow intrusive dependencies.

 As i want minitage.paste to depend on barely nothing else that paster and the minitage core,  i have splitted such 'instances' in an additionnal egg.

 minitage.paste.extras was born.

This package borrow 2 instances at the moment:

• minitage.instances.cas: Install a CAS server
• minitage.instances.openldap: Install an openldap server

Those instances make some nice things as generating on the flag SSL certificates for enabling secured connections to your instance(s).

Thanks to my lovely minitage user remarks, i make some frenglish naming with 'profils' in minitage.paste.

Profils have been renamed to instances as it is more relevant.

paster create -t minitage.profils.env project

become:

paster create -t minitage.instances.env project

In the the last weeks, I carried out some changes to minitage.paste.

Now, there are some new profils out there:

• minitage.profils.mysql : a profil to initiate a mysql database right into your project.
• minitage.profils.openldap : a profil to initiate an openldap instance right into your project.
• minitage.profils.pasteinitd: a profil to generate an init script to launch a server configured via Pythonpaste configuration
  

There also some changes on the postgresql profile.

Now:

• You have your system user admin of the database. But you can connect only via localhost.
• The user created via the paster is only administrator on the database, but not on the database server. He can connect from localhost without password, but he must authenticate from other locations.

Lately, i ran and port problematic packages under FreeBSD. All the packages now seem to install without particular problems.

The tested platform is a FreeBSD-7.1 RELEASE 64 bits.