You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.
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.
When we execute
ansible-container run --production
containers should take on a more "production-like" configuration. Specifically for now:We also talked about splitting Django and Celery into 2 container for both development and production.
The text was updated successfully, but these errors were encountered: