+1 from another dinosaur
Ed
On 16 May 2013, at 16:46, Andy Robinson wrote:
> Speaking as a relatively obsolete dinosaur, I would suggest that if
> you are going to discuss specific deployment practices, you start with
> the most fundamental ones: SSH, the unix shell and so on.
>
> We have had
I would like to second to Andy Robinson here - try to use less new sexy
tools and try to use an existing infrastructure.
For example, how we build & deploy web services*** at YPlan:
1. A bash script is executed (by Jenkins) on a build machine, which
generates an rpm package with [virtualenv + cod
Speaking as a relatively obsolete dinosaur, I would suggest that if
you are going to discuss specific deployment practices, you start with
the most fundamental ones: SSH, the unix shell and so on.
We have had issues over the years with people coming in and
introducing sexy new deployment tools, b
On 16 May 2013, at 11:52, Stestagg wrote:
> The Zope 'brand' got trashed back in the bad old days. If things have truly
> improved, then the sensible thing to do would be to release the new code in a
> way that has no obvious links to the name 'Zope', and let that stand on its
> own merits.
The Zope 'brand' got trashed back in the bad old days. If things have
truly improved, then the sensible thing to do would be to release the new
code in a way that has no obvious links to the name 'Zope', and let that
stand on its own merits.
Another factor here, is that the current trend is towar
On 16 May 2013, at 11:22, Tim Diggins wrote:
> PS at the risk of starting a flame war: "zc.buildout"… --shudder--
> Feels like there are two different python communities sometimes, those that
> use zope-derived rather java-flavoured tools and mindset, and the rest.
I don't want to start a flam
While we're on topic - what would people say is best practice for testing
of a web API in a way that slots cleanly into a CI setup? Lots of different
options out there, hence the q. (I realise this is also a bit like saying
how long is a piece of string)
Michael.
On 15 May 2013 10:57, Harry Per
Harry -
I think if you're teaching best practices on python and testing, you've got
to teach virtualenv - maybe not for deployment (cause better to have
separate VMs for staging and production) but for development and testing,
really important (unless you do everything in a vm, like vagrant or
sim
On 16 May 2013, at 09:02, Harry Percival wrote:
> Overall, it's both reassuring and depressing to hear that that there's no
> single accepted way to do it!
*snip*
because….
> We then start with "provisioning" -- that's getting a server up and running
> with Apache installed. Let's say that'
Hi everyone, thanks for some helpful thoughts!
@Tim, thanks for pointing out the distinction between provisioning and
deployment, I think that's helped to clarify things in my head a little...
@Alfredo, @Kris, and anyone else that's curious, you can already buy/read
the book, plug plug. I'm 6 c
10 matches
Mail list logo
