Seems to work using grokproject-1.0a5dev from trunk with the new configuration.  

(Don't worry about my ramblings about the $'s.  I see now that the first one is removed when grokproject runs and creates the *.conf.in templates.  The second is removed when buildout creates the *.conf files.)

--- On Sun, 8/16/09, Steve Schmechel <email address hidden> wrote:

> From: Steve Schmechel <email address hidden>
> Subject: Re: [Bug 407458] Re: Can not use buildout to configure BLOB storage
> To: <email address hidden>
> Date: Sunday, August 16, 2009, 8:57 AM
> Is there a reason to not just make
> this the default configuration?
> 
> I created a new, no-site-packages virtualenv and new
> grokproject,
> changed the zope.conf.in to use the BLOB storage
> configuration, and it
> runs with no problems and the tests all pass.
> 
> You do get an extra line when you start the project. 
> (Maybe this could
> be suppressed by specifying the layout.):
> 
>   INFO [ZODB.blob] (26577) Blob directory `=
> /opt/grok/atest/blobtest/parts/data/Data.fs/blobs` has
> layout marker
> set. Selected `bushy` layout.
> 
> I'm not saying that this is the way to go - I'm just
> curious what the
> down-side would be to having it able to "just work" when
> you add the
> necessary packages to setup.py and rerun buildout.
> 
> It is unfortunate that the BLOB storage configuration is
> entangled with
> the ZODB file storage configuration in the first place.
> 
> It might actually be nicer if all the database and storage
> related
> configuration occurred in the paster templates as it is
> likely that one
> would have different paths for development and deployment
> anyway.
> 
> That being said, I am OK with the solution as it stands
> right now.
> 
> I will try grokproject and buildout from the trunk code
> later today.  I did my tests with 1.0a4 and did have
> some problems with the changes made in changeset 9926 (the
> double $$ in front of variables).  Buildout passed 
> one of the $'s into the output files, so the paths were
> broken like:
> 
>   path $/opt/grok/atest/blobtest/parts/data/Data.fs
> 
> Maybe this is fixed somewhere else in the trunk.
> 
> Steve
> 
> --- On Sun, 8/16/09, Uli Fouquet <email address hidden>
> wrote:
> 
> > From: Uli Fouquet <email address hidden>
> > Subject: [Bug 407458] Re: Can not use buildout to
> configure BLOB storage
> > To: <email address hidden>
> > Date: Sunday, August 16, 2009, 7:29 AM
> > Just added a commented blob-storage
> > def in grokproject paster template.
> > 
> > What's still missing are hints for blobs-and-ZEO
> > configurations, but
> > this might also give an overload of example configs.
> Maybe
> > we should
> > setup a page describing all the ZODB options somwhere
> on
> > grok.zope.org?
> > Or is there already such a page? I currently  dig
> > component.xml in ZODB
> > repository to lookup all that stuff.
> > 
> > -- 
> > Can not use buildout to configure BLOB storage
> > https://bugs.launchpad.net/bugs/407458
> > You received this bug notification because you are a
> direct
> > subscriber
> > of the bug.
> >
> 
> -- 
> Can not use buildout to configure BLOB storage
> https://bugs.launchpad.net/bugs/407458
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>