Allowing Volumes in projects #18

Author: mcuadros

core/docker.go

@@ -292,6 +292,7 @@ func (d *Docker) startContainer(p *Project, c *Container) error {
 		PortBindings:  ports,
 		RestartPolicy: restartPolicy,
 		Links:         d.formatLinks(p.Links),
+		VolumesFrom:   p.Volumes,
 	})
 }
 

core/docker_test.go

@@ -112,6 +112,7 @@ func (s *CoreSuite) TestDocker_Run(c *C) (p *Project, m *testing.DockerServer, r
 	c.Assert(l[0].IsRunning(), Equals, true)
 	c.Assert(l[0].Names, HasLen, 1)
 	c.Assert(l[0].Names[0], Equals, "/foo")
+
 	return
 }
 

core/project.go

@@ -29,6 +29,7 @@ type Project struct {
 	NoCache             bool
 	Restart             string
 	Ports               []string         `gcfg:"Port"`
+	Volumes             []string         `gcfg:"Volume"`
 	Links               map[string]*Link `json:"-"`
 	LinkNames           []LinkDefinition `gcfg:"Link"`
 	LinkedBy            []*Project       `json:"-"`

documentation/configuration.md

@@ -73,6 +73,7 @@ An environment is a logical group of any number of Docker servers. Dockership su
 * `Port` (multiple, optional): container port to expose, format: `<host-addr>:<host-port>:<container-port>/<proto>` (like -p at `docker run`), additionaly the port can be configured just for one enviroment adding it to end of the port preceded by a `@` (eg: `2.2.2.2:80:80/tcp@live`)
 * `Restart` (optional, default: no): restart policy to apply when a container exits (no, on-failure[:max-retry], always)  (like --restart at `docker run`)
 * `Link` (multiple, optional): creates a Link to other project, when this project is deployed the linked projects are restarted (like -P at `docker run`)
+* `Volume` (multiple, optional): mounts a Data Volume Container (like -v at `docker run`)
 * `GithubToken` (default: Global.GithubToken): the token needed to access this repository, if it is different from the global one.
 * `Environment` (multiple, mandatory): Environment name where this project could be deployed
 * `WebHook` (optional): An HTTP address to which a POST request will be sent when a deploy succeeds for this project. The request will have a JSON object body with keys `previous_revision`, `current_revision`, `project`, `environment` and `errors`.