title: What is the best way to run migrations or load a schema the first time docker-compose up is run?
body: <p>I have a compose setup with two containers, webapp and db. It would be nice if, on first run of  <code>docker-compose up</code>, the migrations/schema in the webapp container would be run. These migrations aren't straight sql, so I can't put them in the db init directory (and they can't be a <code>sh</code> script there either, as they need dependencies not installed on db). </p>
  
  <p>Is there a best practice way to do this, or is it best to just run it as a separate command? Ideally I'd like <code>docker-compose up</code> to be the only command someone like a new dev would need to run to get the whole composition up and running locally, if possible.</p>