Re: [buildout] "private" releases
Wolfgang Schnerring <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
* Christian Theune <[email protected]> [2011-03-30 13:18]: > On 03/30/2011 07:12 AM, Wolfgang Schnerring wrote: > > * Martijn Pieters<[email protected]> [2011-03-29 20:59]: > >> On Tue, Mar 29, 2011 at 14:16, Adam GROSZER<[email protected]> 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 - [email protected] 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 )