Hi Pubudu, Why are we using wso2/wso2base:latest as the base image here? We have to run apt-get update and install subversion anyway right?
IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes etc. and integrate this with WSO2 DepSync. Shall we work on delivering the complete package as well? Thanks. On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka <[email protected]> wrote: > Hi, > > At the moment there is no any official docker image for SVN[1]. I have > created the dockerfile and other relevant artifacts for SVN [2]. This is to > maintain a separate a docker image for SVN for deployment synchronization. > For dep sync in container deployments, there is a mail thread with subject > in [3]. > > Basically rsync is an option for dep sync. But when it compares to SVN, > the following are the main advantages. > > - Can handle several manager nodes > - SVN Container can accommodate multiple products > - We can mount a single volume for SVN server only > > Please share your thoughts. > > [1] - https://hub.docker.com/ > [2] - https://github.com/wso2/dockerfiles/pull/57 > [3] - [Architecture] Dep sync strategies for Carbon 4 products in > Kubernetes > > Thank you! > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
