Many of these are addressed in branch `db/docker-prod` (as well as some other necessary things).
Not done: * a published docker image * svn container * inbound email/DNS routing * download snapshots --- ** [tickets:#7908] Docker setup for production environment** **Status:** open **Milestone:** unreleased **Created:** Mon Jun 29, 2015 03:30 PM UTC by Dave Brondsema **Last Updated:** Sun Apr 24, 2016 05:06 AM UTC **Owner:** nobody We should have a docker/compose configuration that is good for production. Things to include: * production.ini with good settings (including randomized hashes for a value or two in there) * python environment and Allura code bundled into the image (not external volume) * mod_wsgi (express?) or other wsgi server, instead of `paster` * able to make a "release" image that we can publish to dockerhub * git/svn containers, and auth hooked up for that * real email routing, and DNS for e.g. `tickets.myproject.p.mysite.com` * download snapshots enabled * ... Might want to break that down into separate tickets --- Sent from forge-allura.apache.org because dev@allura.apache.org 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.