canmove, Confirmed users
225
edits
| Line 12: | Line 12: | ||
## Investigate using amazon elastic beanstalk to scale docker image creation to one snapshot per commit? | ## Investigate using amazon elastic beanstalk to scale docker image creation to one snapshot per commit? | ||
== | == Identify Registry to Store Docker Images == | ||
=== Private Registry === | |||
If we go with a private registry, this process is already documented in several places: [http://www.activestate.com/blog/2014/01/deploying-your-own-private-docker-registry] [https://blog.codecentric.de/en/2014/02/docker-registry-run-private-docker-image-repository/] | |||
The only upside of a private registry is branding and the possibility of access control for private, security/prototype related debugging/patching of Firefox OS. | |||
=== Public Registry === | |||
If we store docker images in the public docker.io registry then everybody in the Firefox OS community will have access to them. This would be really helpful for getting developers up to speed in a minimum amount of time. | |||
I think for doing a docker image per commit, we should just use the public registry. | |||
== Dockerfile for a B2G Build Image == | == Dockerfile for a B2G Build Image == | ||