> Are you talking about building Docker containers on the fly?
I’m a bit baffled what gave you that idea after I’ve spent days arguing for
strict build/runtime separation?
> We use Docker extensively, but our build machine makes images that we push to
> Dockerhub (private repos). This has a
Bug summary
__
Summary for 2017-02-19 through 2017-02-26
Opened Closed Total Change
Enhancements: 8 3 1346 +5
Defects: 5 3883 +2
Tasks: 1 0
I have a long running twisted pyqt process which occasionally throws a
Received signal 11.
I believe it's in the underlying QtWebEngineView since the twisted process
continues to run. Whatever the reason I would like to figure out a way to
catch this and stop the reactor either in process, or by
On Sat, Feb 25, 2017 at 5:50 PM, Glyph Lefkowitz
wrote:
>
> On Feb 25, 2017, at 9:03 AM, Clayton Daley
> wrote:
>
> Are you talking about building Docker containers on the fly?
>
>
> Pretty sure Hynek has proper build-server/production
> On Feb 25, 2017, at 9:03 AM, Clayton Daley wrote:
>
> Are you talking about building Docker containers on the fly?
Pretty sure Hynek has proper build-server/production separation.
> We use Docker extensively, but our build machine makes images that we push to
>
Are you talking about building Docker containers on the fly? We use Docker
extensively, but our build machine makes images that we push to Dockerhub
(private repos). This has a lot of advantages:
- Our images (on the hub) are effectively pinned at the version they
were built
- Our test
> ... Contrary I’m not a super fan of having one opaque blob on server; the
> transparent structure of a virtualenv is something I learned to appreciate.
> ...
>
> A zipfile containing a virtualenv (pex) isn't all that opaque -- with the
> right editor plugins, you can even *cough* edit the
On 24 February 2017 at 10:25, Hynek Schlawack wrote:
>
> ... Contrary I’m not a super fan of having one opaque blob on server; the
> transparent structure of a virtualenv is something I learned to appreciate.
> ...
>
A zipfile containing a virtualenv (pex) isn't all that opaque --