We need to determine how we want to run the different services (mongo, solr, taskd, mail listener, webapp) since docker prefers one process per host. E.g. the default init scripts for mongo won't run inside docker. We could have a different container for each service, which would illustrate how they can be separate (good for production, complex for local). We might then need a tool like `fig` or `decking` to help orchestrate all those containers together. Or we could make it all run on a single host with one of the `phusion` base images or other workarounds.
--- ** [tickets:#7806] Create a docker image for Allura** **Status:** in-progress **Milestone:** unreleased **Labels:** sf-current sf-2 **Created:** Fri Dec 05, 2014 07:02 PM UTC by Dave Brondsema **Last Updated:** Mon Dec 15, 2014 04:36 PM UTC **Owner:** Dave Brondsema http://blog.dscpl.com.au/2014/12/hosting-python-wsgi-applications-using.html has a good starting point. Would be nice to support development config (supplanting our Vagrant image) as well as a production-ready config (for which we don't have any good docs/images currently) --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
