search

bazooka-ci / bazooka

Continuous Integration and Continuous Deployment Server
http://docs.bazooka-ci.io/
MIT License
60 stars 5 forks source link

Never remove an existing Mongo container #198

Closed haklop closed 9 years ago

julienvey commented 9 years ago

I think it would be better to never remove container "data", but we should be able to remove the container runtime.

I would prefer a volume or a data container to this PR

haklop commented 9 years ago

It should not be the responsibility of Bazooka to manage the database container.

bzk service start starts a Mongo container only for testing purpose and discovering how wonderful is Bazooka ! It doesn't have to administrate the database and cares how the data are stored.

I think that this PR and #199 and another PR adding --links options on bzk service start to link an existing mongo container to the bazooka server is a good solution.

Bazooka can be easily tested with this PR, integrated to an existing Mongo instance/cluster with #199 and attached to a Mongo container with the --links options.