You could have the main process be Supervisord and have it launch two
instances of the Pyramid application, each with a different config
file. I just reviewed a Docker-Django setup, and it had several stages
in the Dockerfile. All of them launched Supervisord and copied all the
job files to the container, but each stage specified in an environment
variable which job files Supervisord should "include" in that
container.
I also have a Pyramid application that's run as two instances with
different config files (main and mobile). I have each one in a
different container using the same image, and a bind-mount directory
that has the config files and launch scripts, so each one specifies a
different launch script or config file on the command line.
I haven't done exactly what you're doing but it sounds like they could
run on different ports in the same container. I have to have them
running on different ports even in different containers. Apache is
running on the host, and the reverse proxies use the ports to access
the containers.
> --
> You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
pylons-discus...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/f51239cb-40c3-4f3d-d52a-7f82b7bce681%40gmail.com.
--
Mike Orr <
slugg...@gmail.com>