Re: [Repoze-dev] News from Plone trunk - Repoze / WSGI
On Sun, 23 Nov 2008 03:46:32 -0800, Martin Aspeli <[EMAIL PROTECTED]> wrote: > In general, having two ways to start the app server is probably a bad > idea. People are bound to get confused. […] > In that case, we have to make a choice: > > - Either, create a "shim" that makes the new install look a lot like > the old one, with ./bin/instance, logs in var/log, etc etc. > > - Or, adopt established conventions, i.e. ./bin/paster serve plone.ini > or whatever, and try to be consistent with Grok, repoze.bfg etc. The Unified Installers have a command "plonectl" which does the right thing no matter what your setup is (ZEO, single instance, etc). Maybe that's the way to do it? -- Alexander Limi · http://limi.net ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] News from Plone trunk - Repoze / WSGI
FTR, building on Hanno's work, I've created an index that allows for the installation of the Zope2 trunk suitable for use with easy_install (requiring no buildout). To do so, I created eggs from the externals used within the buildout directory, and put them in the index. Here's the set of commands that installs Zope2 (snapshot of 2.12 / trunk): $ virtualenv --no-site-packages zope2 $ cd zope2 $ bin/easy_install -i http://dist.repoze.org/zope2/dev/simple repoze.zope2 $ bin/mkzope2instance . $ bin/paster serve etc/zope2.ini Seems to work fine. Nice job Hanno! - C Hanno Schlichting wrote: > Martijn Pieters wrote: >> On Sun, Nov 23, 2008 at 04:01, Hanno Schlichting <[EMAIL PROTECTED]> wrote: - The use of iw.recipe.command means the coredev buildout probably doesn't work on Windows anymore. >>> The exact configuration I built isn't quite what it should end up with. >>> The iw.recipe.command part only creates a Unix-script called instance, >>> which executes "./bin/paster serve etc/plone.ini". The full command >>> works on any platform, the short form is for lazy people on Unix. >> I privately emailed Hanno a different recipe for this part; I already >> implemented something similar in a Jarn Trac buildout using >> zc.recipe.egg. > > Implemented, tested and committed :) > > Hanno > > ___ > Repoze-dev mailing list > Repoze-dev@lists.repoze.org > http://lists.repoze.org/listinfo/repoze-dev > ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] News from Plone trunk - Repoze / WSGI
Martijn Pieters wrote: > On Sun, Nov 23, 2008 at 04:01, Hanno Schlichting <[EMAIL PROTECTED]> wrote: >>> - The use of iw.recipe.command means the coredev buildout probably >>> doesn't work on Windows anymore. >> The exact configuration I built isn't quite what it should end up with. >> The iw.recipe.command part only creates a Unix-script called instance, >> which executes "./bin/paster serve etc/plone.ini". The full command >> works on any platform, the short form is for lazy people on Unix. > > I privately emailed Hanno a different recipe for this part; I already > implemented something similar in a Jarn Trac buildout using > zc.recipe.egg. Implemented, tested and committed :) Hanno ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] News from Plone trunk - Repoze / WSGI
Martin Aspeli wrote: > Hanno Schlichting wrote: >> Martin Aspeli wrote: >>> - The Repoze Zope 2 packaging is maintained outside the Zope core. I >>> don't think we can depend on that long term, though I hope that we'll >>> see a WSGI-capable Zope core before long anyway. >> I don't see a license or legal problem here. From the standpoint of a >> healthy and active community Repoze seems to be better off compared to >> Zope2 ;) > > True, but I'm not sure ChrisM has signed up to make Zope releases for us > forever. I'd be much happier if we were using "the one true Zope" > release, or at least something that promised to become the "one true > Zope" in the mid term future. Ah, I misunderstood your point. We are not using any of the repackaged stuff from repoze. As we have everything egg-based by now, we can use the Zope2 egg (from SVN) and repoze.zope2 directly. There's no zopelib, cmflib or any of the other involved anymore. Hanno ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
