Add step to run django migrations in setup

[danielSbastos]

Hi,
Here we simply add a step in CONTRIBUTING.md to run the project migrations before spinning up the containers.

[cuducos]

Many thanks, but this kind of duplicate this instruction as it is already there a few lines ahead. Any ideas to avoid duplication?

[danielSbastos]

@cuducos, oh, sorry, you're totally right, I must've passed that line while following this guide :/

I'd prefer to leave it here, where I added, because, in my case, after the containers were up, I went to access through the web interface and got an error.

Just a side note, this PR is so small and insignificant, that we could close it, if you'd prefer. I just opened it because I got this error, and thought that other people could have experienced it too, but failed to see that a few lines ahead, the same command was already present.

[cuducos]

I'd prefer to leave it here, where I added, because, in my case, after the containers were up, I went to access through the web interface and got an error.

Totally agree — it makes more sense there. I wouldn't close this PR, just make sure it does not add duplicated instructions ; )

[caiocarrara]

Hi, guys. Perhaps we can put a note on step Installing mentioning the docker-compose up is just a health check to assure all dependencies are succesfully installed and the project is running well. Even though, to run properly jarbas and rosie there are a few more steps (migrations, for example). So we can put a link to the proper sections: Running Rosie and Running Jarbas.

The step without migration is important to isolate installing error from running migration errors.

[danielSbastos]

@cacarrara, nice! I like your approach and idea. Will do :)

[caiocarrara]

LGTM 👏