title: How to handle continuous deployment with docker compose and database services?
body: <p>I'm having a little bit of trouble figuring out how to handle deployment changes on database services. Right now, it's as simple as doing:</p>
  
  <pre><code>docker-compose up -d
  </code></pre>
  
  <p>It rebuilds the containers if there's a change on the config. It's not a problem for my web service (node) since it doesn't have any sort of state. I can pretty much delete everything, bring it back up again and nothing is lost.</p>
  
  <p>My database service is continuously registering new data which is obviously important so i can't just scrap it. As far as I understand, volumes are different every time the images get built. So I would lose all the data every time I rebuild the service.</p>
  
  <p>How should I deal with scheme changes? Or should I update the service manually?</p>