Re: [Zope3-Users] Best Practices - Zopeproject Deployment

2008-05-27 Thread Tim Cook
Hi Kevin, On Mon, 2008-05-26 at 16:58 -0700, Kevin Teague wrote: You can avoid storing user specific information in your buildout.cfg by creating a ~/.buildout/default.cfg file in your home directory that contains user specific information: [buildout] eggs-directory =

Re: [Zope3-Users] Best Practices - Zopeproject Deployment

2008-05-26 Thread Kevin Teague
So, I am now thinking that I will have to have instructions in my installation instructions that tell developers to edit the 'eggs-directory' line; correct? Also they will need to install buildout (or zopeproject) and create a project space before doing the checkout? You can avoid storing

[Zope3-Users] Best Practices - Zopeproject Deployment

2008-05-24 Thread Tim Cook
Hi All, I have a Zope3 project that I started using 'zopeproject'. I now want to deploy this to an SVN server so other developers can checkout and work on the project. After reviewing the zopeproject and buildout docs as well as some examples like z3hello I still cannot decide the correct

Re: [Zope3-Users] Best Practices - Zopeproject Deployment

2008-05-24 Thread Christophe Combelles
Tim Cook a écrit : Hi All, I have a Zope3 project that I started using 'zopeproject'. I now want to deploy this to an SVN server so other developers can checkout and work on the project. After reviewing the zopeproject and buildout docs as well as some examples like z3hello I still cannot

Re: [Zope3-Users] Best Practices - Zopeproject Deployment

2008-05-24 Thread Tim Cook
Hi Christophe, Thanks for your reply. Maybe my question is naive? For background my original zopeproject looked like this below the virtualenv dir: oship-- bin develop-eggs log parts src-- oship (where all the good stuff is located)