(original) (raw)
On Sat, Dec 6, 2014 at 7:27 PM, Wes Turner <wes.turner@gmail.com> wrote:
On Sat, Dec 6, 2014 at 9:07 AM, Donald Stufft <donald@stufft.io> wrote:Heh, one of my thoughts on deploying the bug tracker into production was via a container, especially since we have multiple instances of it. I got side tracked on getting the rest of the infrastructure readier for a web application and some improvements there as well as getting a big postgresql database cluster set up (2x 15GB RAM servers running in Primary/Replica mode). The downside of course to this is that afaik Docker is a lot harder to use on Windows and to some degree OS X than linux. However if the tracker could be deployed as a docker image that would make the infrastructure side a ton easier. I also have control over the python/ organization on Docker Hub too for whatever uses we have for it.Are you referring to https://registry.hub.docker.com/repos/python/ ?IPython / Jupyter have some useful Docker images:CI integration with roundup seems to be the major gap here:
ShiningPandas supports virtualenv and tox, but I don't know how well suited it would be
for fail-fast CPython testing across a grid/graph:
The branch merging workflows of https://datasift.github.io/gitflow/IntroducingGitFlow.html (hotfix/name, feature/name, release/name) are surely portable across VCS systems.