I'm past the rebuild & "paster not found" issues so I won't try to reproduce them again now. Docker Hub will be good to use at some point I think, but I agree its not really needed now.
For mongo: I've got a 20G boot2docker image. `docker-compose run mongo df -h` says: ~~~~ Filesystem Size Used Avail Use% Mounted on none 19G 1.7G 16G 10% / tmpfs 1003M 0 1003M 0% /dev shm 64M 0 64M 0% /dev/shm tmpfs 1.8G 95M 1.7G 6% /data/db /dev/sda1 19G 1.7G 16G 10% /etc/resolv.conf /dev/sda1 19G 1.7G 16G 10% /etc/hostname /dev/sda1 19G 1.7G 16G 10% /etc/hosts tmpfs 1003M 0 1003M 0% /proc/kcore tmpfs 1003M 0 1003M 0% /proc/timer_stats ~~~~ And mongo wants >3G on /data/db, and /data comes from the /allura-data volume right? Where is that set up? --- ** [tickets:#7806] Create a docker image for Allura** **Status:** in-progress **Milestone:** unreleased **Labels:** getting-started sf-current sf-4 **Created:** Fri Dec 05, 2014 07:02 PM UTC by Dave Brondsema **Last Updated:** Mon Jun 08, 2015 11:38 PM UTC **Owner:** Igor Bondarenko 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.
