Production Containers about galaxy HOT 4 CLOSED

From @chargio on October 6, 2017 9:22

👍

from galaxy.

It's still hard to deploy a production Galaxy environment. I had to stand one up for DJ, and had trouble with the following:

• Make var file dynamic, so that there is a version from development and one for production. We'll need to remove the reference from container.yml
• Only load test data if environment is development
• Enable HTTP redirect within nginx. This would be an optional configuration in the event that an external load balancer does not handle this. For example, the AWS load balancer does not seem to have this option.
• Make email validation within the social auth pipeline optional.

from galaxy.

One more thought on this...

We need to have the following:

• Prebaked django and celery images available on Docker Hub
• An installer playbook and documentation similar to AWX that deploys the pre-built images

from galaxy.

closed by #131

from galaxy.