Re: [Zope-dev] [buildout] "private" releases
On 30/03/2011 12:29, Wolfgang Schnerring wrote: >>> (Shameless plug: ;-) gocept.zestreleaser.customupload is a plugin for >>> zest.releaser that allows uploading the created egg via scp. We use this >>> to put our non-public eggs into a folder that's served (and htpasswd >>> protected) by an Apache or somesuch, no complicated "egg server" >>> business required. >> >> So those solutions then require you to put the password for accessing it >> somewhere during deployment ... where is that for you? > > We put the password into the buildout.cfg. lovely.buildouthttp keeps the passwords in a seperate file in yoru .buildout directory... cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [buildout] "private" releases
* Christian Theune [2011-03-30 13:18]: > On 03/30/2011 07:12 AM, Wolfgang Schnerring wrote: > > * Martijn Pieters [2011-03-29 20:59]: > >> On Tue, Mar 29, 2011 at 14:16, Adam GROSZER wrote: > ...and just dump the .tgz sdists in that folder. > >>> Well the problem is that it's not always so simple. > >>> For me a release process is preferably a single command or a single > >>> click on a button. > >> > >> Both zest.releaser and jarn.mkrelease offer you simple single-command > >> release options. I use jarn.mkrelease to make releases to private, > >> password protected folders on our dist.jarn.com 'egg server' (apache > >> directory indexes). > > > > (Shameless plug: ;-) gocept.zestreleaser.customupload is a plugin for > > zest.releaser that allows uploading the created egg via scp. We use this > > to put our non-public eggs into a folder that's served (and htpasswd > > protected) by an Apache or somesuch, no complicated "egg server" > > business required. > > So those solutions then require you to put the password for accessing it > somewhere during deployment ... where is that for you? We put the password into the buildout.cfg. Wolfgang ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [buildout] "private" releases
On 03/30/2011 07:12 AM, Wolfgang Schnerring wrote: > * Martijn Pieters [2011-03-29 20:59]: >> On Tue, Mar 29, 2011 at 14:16, Adam GROSZER wrote: ...and just dump the .tgz sdists in that folder. >>> Well the problem is that it's not always so simple. >>> For me a release process is preferably a single command or a single >>> click on a button. >> >> Both zest.releaser and jarn.mkrelease offer you simple single-command >> release options. I use jarn.mkrelease to make releases to private, >> password protected folders on our dist.jarn.com 'egg server' (apache >> directory indexes). > > (Shameless plug: ;-) gocept.zestreleaser.customupload is a plugin for > zest.releaser that allows uploading the created egg via scp. We use this > to put our non-public eggs into a folder that's served (and htpasswd > protected) by an Apache or somesuch, no complicated "egg server" > business required. So those solutions then require you to put the password for accessing it somewhere during deployment ... where is that for you? -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting, development, hosting, operations ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [buildout] "private" releases
* Martijn Pieters [2011-03-29 20:59]: > On Tue, Mar 29, 2011 at 14:16, Adam GROSZER wrote: >>> ...and just dump the .tgz sdists in that folder. >> Well the problem is that it's not always so simple. >> For me a release process is preferably a single command or a single >> click on a button. > > Both zest.releaser and jarn.mkrelease offer you simple single-command > release options. I use jarn.mkrelease to make releases to private, > password protected folders on our dist.jarn.com 'egg server' (apache > directory indexes). (Shameless plug: ;-) gocept.zestreleaser.customupload is a plugin for zest.releaser that allows uploading the created egg via scp. We use this to put our non-public eggs into a folder that's served (and htpasswd protected) by an Apache or somesuch, no complicated "egg server" business required. Wolfgang ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [buildout] "private" releases
On Tue, Mar 29, 2011 at 14:16, Adam GROSZER wrote: > Well the problem is that it's not always so simple. > For me a release process is preferably a single command or a single > click on a button. Both zest.releaser and jarn.mkrelease offer you simple single-command release options. I use jarn.mkrelease to make releases to private, password protected folders on our dist.jarn.com 'egg server' (apache directory indexes). -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [buildout] "private" releases
Hello, On Fri, 25 Mar 2011 19:24:05 + you wrote: > > Hi Christian, > > On 25/03/2011 16:49, Christian Theune wrote: >> the German speaking Zope Users Group (DZUG e.V.) organizes a series of 4 >> sprints this year to support feature development within the proximity of >> the ZTK and solve problems encountered by Zope, Plone and Python developers. >> > >> Topics >> == >> >> * Discussing how to deal with "private" releases > > FWIW, I've had no problems with this, here's a sample buildout.cfg: > > [buildout] > extensions = lovely.buildouthttp > find-links = https://example.com/password/protected/folder > > ...and just dump the .tgz sdists in that folder. > > Of course, if you don't need password protection such as when you have > your "egg server" on a private network, you just need the find-links. > > I'm not really sure why people have written a complicated array of "egg > servers" and the like when a simple http or file system served folder is > just fine ;-) Well the problem is that it's not always so simple. For me a release process is preferably a single command or a single click on a button. -- Best regards, Adam GROSZER -- Quote of the day: To look up and not down, To look forward and not back, To look out and not in, and To lend a hand. - Edward Everett Hale ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [buildout] "private" releases
Hi Christian, On 25/03/2011 16:49, Christian Theune wrote: > the German speaking Zope Users Group (DZUG e.V.) organizes a series of 4 > sprints this year to support feature development within the proximity of > the ZTK and solve problems encountered by Zope, Plone and Python developers. > > Topics > == > > * Discussing how to deal with "private" releases FWIW, I've had no problems with this, here's a sample buildout.cfg: [buildout] extensions = lovely.buildouthttp find-links = https://example.com/password/protected/folder ...and just dump the .tgz sdists in that folder. Of course, if you don't need password protection such as when you have your "egg server" on a private network, you just need the find-links. I'm not really sure why people have written a complicated array of "egg servers" and the like when a simple http or file system served folder is just fine ;-) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
